Hello, I tried to reproduce the issue in my environment with:
i=0;while true;do python -m pytest tests;ret=$?;i=$[ $i+1 ];echo "Run: $i"; [ $ret -ne 0 ] && break; done and in similar way with pbuilder that I am using and FTBFS didn't ever happen (tried 50+ builds). I have suspicion that these test failures occurs only on slower, eg. one CPU machines as something similar happens with vdirsyncer as well. Unfortunately running tests during build is always fragile and it seems that what's working in one environment may be FTBFS for anyone else :-( I will give it some more time to debug and reproduce (can you try the same test on VM with more than 1 CPU?) But as both CI and reproducible builds are passing fine, I would suggest lowering the severity as this issue doesn't seem to be critical enough to automatically remove package from testing. Filip
signature.asc
Description: Digital signature
