Your message dated Thu, 12 Sep 2024 11:37:16 +0000
with message-id <e1soi8s-00bu19...@fasolo.debian.org>
and subject line Bug#1081459: fixed in mpi4py 4.0.0-3
has caused the Debian Bug report #1081459,
regarding FTBFS: test_util_pool fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1081459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-mpi4py
Version: 4.0.0-2
Severity: serious
Tags: ftbfs
Justification: FTBFS
Control: forwarded -1 https://github.com/mpi4py/mpi4py/issues/545
mpi4py 4 was building fine in experimental but shows tests error in
unstable:
testTestAll (test_util_pkl5.TestPKL5World.testTestAll) ... ok
testWaitAll (test_util_pkl5.TestPKL5World.testWaitAll) ... ok
test_apply (test_util_pool.TestProcessPool.test_apply) ... [sbuild:00243] 1
more process has sent help message help-mca-bml-r2.txt / unreachable proc
[sbuild:00483] [[13078,42],0] ORTE_ERROR_LOG: Unreachable in file
../../../ompi/dpm/dpm.c at line 493
[sbuild:00242] [[13078,1],0] ORTE_ERROR_LOG: Unreachable in file
../../../ompi/dpm/dpm.c at line 493
Exception in thread Thread-6 (_manager_spawn):
Traceback (most recent call last):
File "/usr/lib/python3.12/threading.py", line 1075, in _bootstrap_inner
self.run()
File "/usr/lib/python3.12/threading.py", line 1012, in run
self._target(*self._args, **self._kwargs)
File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures/_core.py",
line 350, in _manager_spawn
comm = serialized(client_spawn)(pyexe, pyargs, nprocs, info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures/_core.py",
line 1058, in client_spawn
comm = MPI.COMM_SELF.Spawn(python_exe, args, max_workers, info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "src/mpi4py/MPI.src/Comm.pyx", line 2544, in mpi4py.MPI.Intracomm.Spawn
with nogil: CHKERR( MPI_Comm_spawn(
mpi4py.MPI.Exception: MPI_ERR_INTERN: internal error
[sbuild:00243] 1 more process has sent help message help-mca-bml-r2.txt /
unreachable proc
[sbuild:00243] 1 more process has sent help message help-mpi-runtime.txt /
mpi_init:startup:internal-failure
[sbuild:00243] 1 more process has sent help message help-mpi-errors.txt /
mpi_errors_are_fatal unknown handle
E: Build killed with signal TERM after 150 minutes of inactivity
The error is intermittent, indicating a race condition (may pass
after trying the build again).
Upstream acknowledges spawn is flakey in OpenMPI 4 (likely fixed in
OpenMPI 5), but the suggested workaround MPI4PY_TEST_SPAWN=false does
not prevent spawn tests from launching.
-- 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.10.6-amd64 (SMP w/8 CPU threads; PREEMPT)
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 python3-mpi4py depends on:
ii libc6 2.40-2
ii libopenmpi3t64 4.1.6-13.3
ii mpi-default-bin 1.17
ii python3 3.12.5-1
python3-mpi4py recommends no packages.
Versions of packages python3-mpi4py suggests:
ii python3-numpy 1:1.26.4+ds-11
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 4.0.0-3
Done: Drew Parsons <dpars...@debian.org>
We believe that the bug you reported is fixed in the latest version of
mpi4py, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1081...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons <dpars...@debian.org> (supplier of updated mpi4py package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 12 Sep 2024 09:33:57 +0200
Source: mpi4py
Architecture: source
Version: 4.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Drew Parsons <dpars...@debian.org>
Closes: 1081459
Changes:
mpi4py (4.0.0-3) unstable; urgency=medium
.
* Apply MPI4PY_TEST_SPAWN=false with tests on all arches to avoid
spawn failures with OpenMPI 4. Requires GITHUB_ACTIONS=true to
activate. Spawn is generally flakey with OpenMPI 4. Reenable
spawn tests later with OpenMPI 5. Closes: #1081459.
Checksums-Sha1:
f129ec2e39de3567394d41aa7c51b022c1aa535f 2510 mpi4py_4.0.0-3.dsc
031b3461fab15e9523fde0047e9d4af2338aae34 12468 mpi4py_4.0.0-3.debian.tar.xz
Checksums-Sha256:
8ce0fc5eecb7d0bcf35fb93b054e01c91a79dd3ae98b0bff1c8cd56eba83f7c7 2510
mpi4py_4.0.0-3.dsc
fa47796ee0fc15c5f7e57cfcd80d58e979152124f2d0e6b820cff83b6012f97b 12468
mpi4py_4.0.0-3.debian.tar.xz
Files:
57b3b370f6a3658fb0b6bb2b54235a92 2510 python optional mpi4py_4.0.0-3.dsc
bcdf7838e976b5fd2ac1182656c08cbf 12468 python optional
mpi4py_4.0.0-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmbizb8ACgkQVz7x5L1a
AfpV3w//f1jirzQk084Pa5g/7LKwkQhOV7Dn/+5w1zFauutALK4qIyUOZJ/PFmzA
cp2iMXhJLiIFqywku6V+urGH0puTD6PODfqhycATkKVoLlvxeNaNKMGsa92G4p01
mXsSADDmcrKvCIAGhpXGdC+k+J+7TO1DViBlFZRFq96nUuB5yIuIdpAYJ0M3ZJvz
7LdUOoZ4ztmvwkGPgPvXW9lfz0wVdOrJBKeuL0gGDVNx4for0CUH0VyO4S4iqEPa
zXao3CZOgFQFyJ4s6Ndifw4h0JEPeYEwlP/Dq15106tE2xArfeHkbROVfgJjkb53
yrHVWN5gdwkU5FrCZLP8M+Yqa62GPQYH1cWrqsiHeWBOxLATPhjIiVVbXj7JExgY
rdGocVIufyFer9XLtoDRH60RLfUs5azAHCUxqlR5sShl/Hy4di9N2w81o0w4sxWj
N3eXmL8NnJoPTVZtrLuJWm6RDMzC0HKWC3ktCixtaVbmW49O5LhOMKuFmawL7uVm
f/zP7Ze39pzCMCwu9mpTyT1osXIph52wNCv+pwTtWgKBXVlEJxp0iY0GJ7krgxrQ
ar9z6ZmGC+Y1PLtXWFiGTk/i+NTHydETielt31qwsExp9pQr5vsKyyCwGVESflSI
V8NAawri0gEj/+RxDqMfNu/34gUGJX26YIt8GIwz1Cg77RVpDd8=
=33DY
-----END PGP SIGNATURE-----
pgpxOSTRdfXY6.pgp
Description: PGP signature
--- End Message ---
