[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Any clue how to circumvent issues with MPI on autobuilders



On Fri, Sep 14, 2018 at 9:21 AM, Andreas Tille <andreas@an3as.eu> wrote:
Control: tags -1 help

Hi,

in the bug log of #906337 the test suite aborts with

...
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------
E: Build killed with signal TERM after 60 minutes of inactivity
--------------------------------------------------------------------------------
...


Since I have no experience with MPI but I know that on Debian Science
are people with experience hanging around, I take the freedom to ask
here for help.  I suspect that the test suite assumes some MPI features
which are not available on any autobuilder machine.  Any idea what to
do in this case?

In debian/rules in dolfin, we use the following to allow test programs to run with OpenMPI:

  export OMPI_MCA_plm_rsh_agent=/bin/false

Maybe that will fix your problem.

Johannes

Reply to: