On Thu, 12 Oct 2017 at 01:37:51 +0100, Simon McVittie wrote:
> On mips64el there are a couple of timeouts (knowing mips*, probably
> an arbitrary timeout is just too short):
>
> TEST-UNEXPECTED-FAIL | js1_5/Array/regress-157652.js | (args: "") | (TIMEOUT)
> TEST-UNEXPECTED-FAIL | js1_5/Regress/regress-422348.js | (args: "") |
> (TIMEOUT)
>
> and one more interesting-looking failure:
>
> ## ecma_6/Array/for_of_1.js: rc = 3, run time = 0.483245
> ecma_6/Array/for_of_1.js:100:5 Error: Assertion failed: got 150, expected 300
> Stack:
> TestChangeArrayPrototype@ecma_6/Array/for_of_1.js:100:5
> @ecma_6/Array/for_of_1.js:102:1
> TEST-UNEXPECTED-FAIL | ecma_6/Array/for_of_1.js | (args: "")
I've committed changes to pkg-gnome git to make these failures
non-fatal, and will downgrade the severity of this bug to non-RC when
those changes have been released.
The test failures clearly indicate at least one 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 mips64el users can provide would be
appreciated. If the bug(s) isn't/aren't fixed, mozjs52 will either
remain available with known test failures if it does basically work,
or have its old binaries removed from mips64el (with the test failures
becoming a FTBFS) if feedback indicates that the test failures
are evidence of RC bugs.
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.
Thanks,
smcv
