Hi, On Mon, 23 Mar 2026 19:08:22 +0100 Drew Parsons <[email protected]> wrote:
However, on debci the tests are now hanging at test_cco_buf.TestCCOBufWorld.testAllreduce after hitting an ERROR in test_cco_buf.TestCCOBufWorld.testAllgather so debci fails on timeout, https://ci.debian.net/data/autopkgtest/testing/i386/m/mpi4py/69692323/log.gzI suspect the timeout in testAllreduce is indirectly triggered by the error in testAllgather. I can't see what the substantial difference between the two test environments is. Why are the same tests passing on barriere, but hitting an error and failing with timeout on debci?
I tried it on my own laptop: paul@toba ~ $ sudo autopkgtest-build-lxc debian unstable i386 paul@toba ~ $ autopkgtest mpi4py -- lxc --sudo autopkgtest-unstable-i386and that also passed. I'm wondering if the number of cpu's matter (our i386 workers only have 2).
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- debian-science-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
