Your message dated Sun, 17 Nov 2024 21:13:40 +0100
with message-id <E1tCleP-000000068rr-04Gj@sandy>
and subject line Re: Bug#948655 mpi4py: FTBFS on all ppc arches: tests fail:
testCreateF90{Complex,Real}Double
has caused the Debian Bug report #948655,
regarding mpi4py: FTBFS on all ppc arches: tests fail:
testCreateF90{Complex,Real}Double
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.)
--
948655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpi4py
Version: 3.0.3-2
Severity: normal
Control: forwarded -1
https://bitbucket.org/mpi4py/mpi4py/issues/127/test-failure-with-openmpi-on-ppc64le
mpi4py FTBFS on all powerpc arches (ppc64el, powerpc and ppc64) due to
failing fortran double tests:
======================================================================
ERROR: testCreateF90ComplexDouble (test_datatype.TestDatatype)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/<<PKGBUILDDIR>>/test/test_datatype.py", line 324, in
testCreateF90ComplexDouble
self.check_datatype(None, factory, *args)
File "/<<PKGBUILDDIR>>/test/test_datatype.py", line 144, in check_datatype
newtype = factory(*args)
File "mpi4py/MPI/Datatype.pyx", line 309, in
mpi4py.MPI.Datatype.Create_f90_complex
mpi4py.MPI.Exception: MPI_ERR_ARG: invalid argument of some other kind
======================================================================
ERROR: testCreateF90RealDouble (test_datatype.TestDatatype)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/<<PKGBUILDDIR>>/test/test_datatype.py", line 306, in
testCreateF90RealDouble
self.check_datatype(None, factory, *args)
File "/<<PKGBUILDDIR>>/test/test_datatype.py", line 144, in check_datatype
newtype = factory(*args)
File "mpi4py/MPI/Datatype.pyx", line 300, in
mpi4py.MPI.Datatype.Create_f90_real
mpi4py.MPI.Exception: MPI_ERR_ARG: invalid argument of some other kind
The error did not occur with OpenMPI 3, it is triggered by OpenMPI 4.
The problem has already been reported upstream at
//bitbucket.org/mpi4py/mpi4py/issues/127/test-failure-with-openmpi-on-ppc64le
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Upstream asserts this is not a bug in mpi4py. Perhaps powerpc now passes with
mpich,
we didn't test that.
debian patch skip_ppc_failing_tests.patch allows successful build
by skipping the failing tests. So we can close this bug now.
--- End Message ---
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
