Your message dated Fri, 10 Aug 2018 11:52:14 +0100
with message-id <>
and subject line Re: Bug#878319: mozjs52: tests fail on ppc64el: timeout
has caused the Debian Bug report #878319,
regarding mozjs52: tests fail on ppc64el: timeout
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Source: mozjs52
Version: 52.3.1-4
Severity: normal

Build-time test suite failures for mozjs52 have been made non-fatal on
ppc64el because the tests time out. This is clearly a bug, but it isn't
clear what the severity of that bug is: it could be anything from minor
(if trivial functionality is broken) to RC (if mozjs52 is basically
unusable on this architecture).

Any testing and patches that ppc64el users can provide would be
appreciated. If it isn't fixed, depending on feedback about the severity
of whatever underlying bug is causing these test failures, mozjs52 will
either remain available with known test failures, or be removed from
ppc64el (with the test failures becoming a FTBFS).

mozjs52 is used by current versions of gjs, so architecture-specific
removal of mozjs52 would also require architecture-specific removal of
gnome-shell, gnome-maps, polari etc., which would in turn make the
GNOME task and metapackages uninstallable on this architecture.


--- End Message ---
--- Begin Message ---
Version: 52.3.1-9

On Thu, 12 Oct 2017 at 20:51:59 +0100, Simon McVittie wrote:
> Build-time test suite failures for mozjs52 have been made non-fatal on
> ppc64el because the tests time out.

According to buildd logs and #905199, this seems to have been fixed,
so I'm going to try making test failures fatal on ppc64el again.

On Mon, 18 Dec 2017 at 20:03:25 +0100, John Paul Adrian Glaubitz wrote:
> Did you check whether there might be any relevant patches in Firefox
> upstream which address the issue?

We now have a newer mozjs (mozjs52 52.9.1-1, and I'm preparing mozjs60
for submission to NEW) so hopefully we have picked up improvements
from upstream. While preparing mozjs60 I checked for relevant patches in
firefox-esr v60's debian/patches and didn't see any.


--- End Message ---

Reply via email to