Package: src:mpi4py
Version: 2.0.0-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
dh build-indep --with python2,python3,autoreconf,sphinxdoc --buildsystem 
python_distutils
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_autoreconf debian/rules -- cythonize
make[2]: Entering directory '/<<PKGBUILDDIR>>'
D: removing previously generated by Cython sources
find -iname *.c | xargs grep -l 'Generated by Cython' | xargs -r rm
python setup.py build_src
running build_src
cythonizing 'mpi4py.MPI.pyx' -> 'mpi4py.MPI.c'

[... snipped ...]

    MPI.Win.Create(None, 1, MPI.INFO_NULL, MPI.COMM_SELF).Free()
  File "MPI/Win.pyx", line 73, in mpi4py.MPI.Win.Create 
(src/mpi4py.MPI.c:123760)
Exception: MPI_ERR_WIN: invalid window

======================================================================
ERROR: Failure: Exception (MPI_ERR_WIN: invalid window)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
    addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
    return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
    mod = load_module(part_fqname, fh, filename, desc)
  File "/<<PKGBUILDDIR>>/test/test_subclass.py", line 241, in <module>
    MPI.Win.Create(MPI.BOTTOM).Free()
  File "MPI/Win.pyx", line 73, in mpi4py.MPI.Win.Create 
(src/mpi4py.MPI.c:123760)
Exception: MPI_ERR_WIN: invalid window

======================================================================
ERROR: Failure: Exception (MPI_ERR_WIN: invalid window)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
    addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
    return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
    mod = load_module(part_fqname, fh, filename, desc)
  File "/<<PKGBUILDDIR>>/test/test_win.py", line 242, in <module>
    MPI.Win.Create(MPI.BOTTOM, 1, MPI.INFO_NULL, MPI.COMM_SELF).Free()
  File "MPI/Win.pyx", line 73, in mpi4py.MPI.Win.Create 
(src/mpi4py.MPI.c:123760)
Exception: MPI_ERR_WIN: invalid window

----------------------------------------------------------------------
Ran 815 tests in 5.354s

FAILED (errors=8)
[linode1:05869] 4 more processes have sent help message help-osc-pt2pt.txt / 
mpi-thread-multiple-not-supported
debian/rules:89: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules:22: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------

This is just how the build ends, not necessarily the relevant part.

This started to happen in stretch somewhere between 2017-02-19 and 2017-02-24,
so I suspect of some build-dependency changing behaviour.

I can provide a full build log if you need, but it also fails here in
both testing and unstable:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mpi4py.html

so I expect this to be easy to reproduce.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Reply via email to