Bug#1131533: mpich breaks mpi4py autopkgtest str2bool[supported] == False

[Paul Gevers]

Hi,

On Mon, 23 Mar 2026 19:08:22 +0100 Drew Parsons <dparsons at debian.org> 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.gz
> 
> I 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 at toba ~ $ sudo autopkgtest-build-lxc debian unstable i386
paul at toba ~ $ autopkgtest mpi4py -- lxc --sudo autopkgtest-unstable-i386

and that also passed. I'm wondering if the number of cpu's matter (our 
i386 workers only have 2).

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 585 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20260329/e8da943a/attachment.sig>