Bug#873780: mozjs52: FTBFS on kfreebsd-amd64: tests time out
Simon McVittie
smcv at debian.org
Thu Oct 12 22:35:28 UTC 2017
Control: tags 873780 + unreproducible help
On Wed, 30 Aug 2017 at 22:38:39 -0400, Aaron M. Ucko wrote:
> Version: 52.3.1-3
>
> The build of mozjs52 for kfreebsd-amd64 (admittedly not a release
> architecture) failed:
>
> TEST-KNOWN-FAIL | ecma_7/TypedObject/memory.js | (args: "") | (SKIP)
> TEST-PASS | ecma_7/Syntax/non-simple-with-strict-directive.js | (args: "")
> E: Caught signal ‘Terminated’: terminating immediately
> [...]
> Build killed with signal TERM after 150 minutes of inactivity
This doesn't seem to happen any more with 52.3.1-4; instead, some tests
fail (#878331). I'm marking the bug as unreproducible rather than closing
it, because I have no idea why 52.3.1-4 would fix this, and my only
evidence that it's fixed is one buildd log per kfreebsd port.
The test failures are now considered non-fatal on kfreebsd-*, so they will
not cause FTBFS unless this timeout condition (or one like it) comes back.
I don't think the GNOME maintainers are likely to put time into fixing
this, but if someone has a reasonable patch, applying it should be fine;
tagging + help accordingly.
smcv
More information about the pkg-gnome-maintainers
mailing list