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 <bi...@debian.org> wrote: > On Thu, 12 Oct 2017 20:51:59 +0100 Simon McVittie <s...@debian.org> wrote: > > Source: mozjs52 > > Version: 52.3.1-4 > > Severity: normal > > X-Debbugs-Cc: debian-powerpc@lists.debian.org > > > > 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? >
pgpvKju2u78Ky.pgp
Description: PGP signature
