On Sat, Apr 11, 2020 at 10:59:56AM +0200, Laurent Bigonville wrote: > On Sat, 11 Apr 2020 10:38:52 +0200 Laurent Bigonville <bi...@debian.org> > wrote: > > > I'm not exactly sure what's going on here > > Disabling running the tests in parallel (--no-parallel to dh_auto_test) > seems to fix the issue
Indeed, I just forced parallel=1 on the buildd (kamp) for dbus-python and the builds succeeded. If it helps anyone debugging this, kamp has 2 i7-4790K cores allocated to it, which is a desktop processor not a server processor so has a higher clock speed (and despite being a 2014 model performs very well; this buildd alone can easily keep up with both kfreebsd-amd64 and kfreebsd-i386). The buildd is also configured with parallel=2, and has a habit of exposing race conditions in test scripts...