Package: mpich Version: 4.3.0-3 Severity: serious Justification: FTBFS The new mpich 4.3.0 is doing something different with GPUs that is causing test failures.
mpich itself was affected, Bug#1100880, but 4.3.0-3 hid the problem by disabling GPU support in autopkgtests. That doesn't help other packages though. For instance armci-mpi FTBFS due to failing tests: FAIL: benchmarks/ping-pong ========================== Abort(336718351): Fatal error in internal_Init: Other MPI error, error stack: internal_Init(70)....: MPI_Init(argc=0x7fff9ad896bc, argv=0x7fff9ad896b0) failed MPII_Init_thread(199): MPII_init_gpu(51)....: gpu_init failed Abort(336718351): Fatal error in internal_Init: Other MPI error, error stack: internal_Init(70)....: MPI_Init(argc=0x7fff26efca8c, argv=0x7fff26efca80) failed MPII_Init_thread(199): MPII_init_gpu(51)....: gpu_init failed FAIL benchmarks/ping-pong (exit status: 15) -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.20-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mpich depends on: ii hwloc 2.12.0-1 ii libamdhip64-5 5.7.1-5+b1 ii libc6 2.41-6 ii libhwloc15 2.12.0-1 ii libmpich12 4.3.0-3 ii libslurm42t64 24.11.3-2 ii perl 5.40.1-2 Versions of packages mpich recommends: ii libmpich-dev 4.3.0-3 Versions of packages mpich suggests: ii mpich-doc 4.3.0-3 -- no debconf information
