Acknowledgement sent
to Laurent Bigonville <[email protected]>:
New Bug report received and forwarded. Copy sent to Utopia Maintenance Team <[email protected]>.
(Sat, 11 Apr 2020 08:42:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Laurent Bigonville <[email protected]>:
Extra info received and forwarded to list. Copy sent to Utopia Maintenance Team <[email protected]>.
(Sat, 11 Apr 2020 09:03:02 GMT) (full text, mbox, link).
Subject: Re: Tests failures on kfreebsd architectures
Date: Sat, 11 Apr 2020 10:59:56 +0200
On Sat, 11 Apr 2020 10:38:52 +0200 Laurent Bigonville <[email protected]>
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
Acknowledgement sent
to Jessica Clarke <[email protected]>:
Extra info received and forwarded to list. Copy sent to Utopia Maintenance Team <[email protected]>.
(Sat, 11 Apr 2020 11:57:03 GMT) (full text, mbox, link).
Subject: Re: Bug#956438: Tests failures on kfreebsd architectures
Date: Sat, 11 Apr 2020 12:54:57 +0100
On Sat, Apr 11, 2020 at 10:59:56AM +0200, Laurent Bigonville wrote:
> On Sat, 11 Apr 2020 10:38:52 +0200 Laurent Bigonville <[email protected]>
> 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...
Acknowledgement sent
to Simon McVittie <[email protected]>:
Extra info received and forwarded to list. Copy sent to Utopia Maintenance Team <[email protected]>.
(Sat, 11 Apr 2020 12:21:03 GMT) (full text, mbox, link).
Subject: Re: Bug#956438: Tests failures on kfreebsd architectures
Date: Sat, 11 Apr 2020 13:19:49 +0100
On Sat, 11 Apr 2020 at 12:54:57 +0100, Jessica Clarke wrote:
> 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...
If there's an incompatibility for two of the tests running in parallel,
I'm surprised not to have seen it on any of the Linux machines where
I've been building dbus-python in parallel mode for several years.
Presumably this is kFreeBSD-specific, but I can't think of a reason why
it would be...
smcv