Hello, Matthias Klose, le ven. 22 mars 2024 03:29:04 +0100, a ecrit: > On 22.03.24 01:22, Samuel Thibault wrote: > > Matthias Klose, le ven. 22 mars 2024 01:11:09 +0100, a ecrit: > > > these tests also fail with openmpi on amd64 and ppc64el > > > > ? I can't reproduce this. > > sorry, only saw that for an Ubuntu build: > https://launchpad.net/ubuntu/+source/eztrace/2.1-7ubuntu3
Ok. These failures look extremely odd. > Running mpirun.openmpi --oversubscribe -np 2 > /<<PKGBUILDDIR>>/build-openmpi/src/eztrace -p -t openmpi ./mpi_ping 2: Eztrace test Mode 2: Eztrace test Mode 2: Abort(336163333) on node 0: Fatal error in internal_Comm_size: Invalid communicator, error stack: 2: internal_Comm_size(30769): MPI_Comm_size(comm=0xb6061990, size=0xffffb86caa54) failed 2: internal_Comm_size(30723): Invalid communicator The program has basically only called int comm_size = -1; MPI_Init(&argc, &argv); MPI_Comm_size(MPI_COMM_WORLD, &comm_size); Which is essentially a smoketest for a working mpi implementation. And these error messages are coming from mpich, not from openmpi! I'm wondering if ubuntu is perhaps mixing libmpi from mpich and from openmpi? > but please could you run all three testsuites, and only then fail the build? Done so in the git tree. I have also added a smoketest for working MPI implementations (without any use of eztrace). Samuel
