Source: esys-particle Version: 2.3.4+dfsg1-2 Severity: serious Justification: makes the package in question unusable or mostly so Control: block 836917 by -1
Dear Maintainer, The upload of openmpi (2.0.1-3) to unstable has triggered an uncoordinated transition (#836917). Unfortunately your package FTBFS due to test failures: cd /«BUILDDIR»/esys-particle-2.3.4+dfsg1/debian/test; mpirun --allow-run-as-root -np 3 /«BUILDDIR»/esys-particle-2.3.4+dfsg1/debian/esys-particle/usr/bin/esysparticle compression.py; cat nbons.dat; cat ekin.dat; cat epot.dat [babin:06791] PMIX ERROR: INVALID-CREDENTIAL in file src/server/pmix_server_listener.c at line 540 [babin:06796] PMIX ERROR: UNREACHABLE in file src/client/pmix_client.c at line 983 [babin:06796] PMIX ERROR: UNREACHABLE in file src/client/pmix_client.c at line 199 *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, *** and potentially your MPI job) [babin:6796] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "(null)" (-43) instead of "Success" (0) -------------------------------------------------------------------------- ------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code.. Per user-direction, the job has been aborted. ------------------------------------------------------- -------------------------------------------------------------------------- mpirun detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[38239,1],0] Exit code: 1 -------------------------------------------------------------------------- cat: nbons.dat: No such file or directory cat: ekin.dat: No such file or directory cat: epot.dat: No such file or directory Kind Regards, Bas -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
