Re: mozjs52: tests fail on ppc64el: timeout

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: mozjs52: tests fail on ppc64el: timeout

Michael Biebl-3
On Thu, 12 Oct 2017 20:51:59 +0100 Simon McVittie <[hidden email]> wrote:

> Source: mozjs52
> Version: 52.3.1-4
> Severity: normal
> X-Debbugs-Cc: [hidden email]
>
> 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).
>
The tests that currently fail are

> ## js1_5/extensions/regress-341956-01.js: rc = 0, run time = 233.1152
> BUGNUMBER: 341956
> STATUS: GC Hazards in jsarray.c - unshift
>  FAILED! [reported from test()] GC Hazards in jsarray.c - unshift : Expected value 'true', Actual value 'false'
> Done
> TEST-UNEXPECTED-FAIL | js1_5/extensions/regress-341956-01.js | (args: "")


> ## js1_5/extensions/regress-313763.js: rc = 0, run time = 375.610908
> BUGNUMBER: 313763
> STATUS: Root jsarray.c creatures
> STATUS: This bug requires TOO_MUCH_GC
> STATUS: false
>  FAILED! [reported from top level script] Root jsarray.c creatures : Type mismatch, expected type string, actual type undefined Expected value '1', Actual value 'undefined'
> TEST-UNEXPECTED-FAIL | js1_5/extensions/regress-313763.js | (args: "")


--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?


signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: mozjs52: tests fail on ppc64el: timeout

Frédéric Bonnard-2
Hi,
to give a small update on this, I noticed that the getter functions
defined just don't get called, thus the test failing.
Also this works fine when optimisation is disabled for the build.
I'll dig more and try to have some more details on this.

F.

On Fri, 20 Oct 2017 22:35:51 +0200, Michael Biebl <[hidden email]> wrote:

> On Thu, 12 Oct 2017 20:51:59 +0100 Simon McVittie <[hidden email]> wrote:
> > Source: mozjs52
> > Version: 52.3.1-4
> > Severity: normal
> > X-Debbugs-Cc: [hidden email]
> >
> > 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).
> >
>
> The tests that currently fail are
>
> > ## js1_5/extensions/regress-341956-01.js: rc = 0, run time = 233.1152
> > BUGNUMBER: 341956
> > STATUS: GC Hazards in jsarray.c - unshift
> >  FAILED! [reported from test()] GC Hazards in jsarray.c - unshift : Expected value 'true', Actual value 'false'
> > Done
> > TEST-UNEXPECTED-FAIL | js1_5/extensions/regress-341956-01.js | (args: "")
>
>
> > ## js1_5/extensions/regress-313763.js: rc = 0, run time = 375.610908
> > BUGNUMBER: 313763
> > STATUS: Root jsarray.c creatures
> > STATUS: This bug requires TOO_MUCH_GC
> > STATUS: false
> >  FAILED! [reported from top level script] Root jsarray.c creatures : Type mismatch, expected type string, actual type undefined Expected value '1', Actual value 'undefined'
> > TEST-UNEXPECTED-FAIL | js1_5/extensions/regress-313763.js | (args: "")
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>

attachment0 (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: mozjs52: tests fail on ppc64el: timeout

John Paul Adrian Glaubitz
Hi Frédéric!

On 12/18/2017 05:31 PM, Frédéric Bonnard wrote:
> to give a small update on this, I noticed that the getter functions
> defined just don't get called, thus the test failing.
> Also this works fine when optimisation is disabled for the build.
> I'll dig more and try to have some more details on this.

Did you check whether there might be any relevant patches in Firefox
upstream which address the issue? For example, I know that mozjs52 is
missing some upstream fixes contributed by me to several Debian
architectures. Several of these fixes are missing in mozjs52.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - [hidden email]
`. `'   Freie Universitaet Berlin - [hidden email]
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Reply | Threaded
Open this post in threaded view
|

Re: Bug#878319: mozjs52: tests fail on ppc64el: timeout

Simon McVittie-7
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.

    smcv