Frequent but intermittent bug913749.js:18:1 Error: Assertion failed: got "y.length is undefined", expected "y is undefined"

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
4 years ago
4 years ago

People

(Reporter: KWierso, Unassigned)

Tracking

({intermittent-failure})

37 Branch
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

4 years ago
This started showing up today. I first saw it on inbound on the backout of bug 1073816, but then I saw it on b2g-inbound on the merge from m-c, which didn't include bug 1073816 or its backout.
TEST-PASS | js/src/jit-test/tests/ion/bug911707.js | Success (code 0, args "--ion-eager --no-baseline --no-ion")
TEST-PASS | js/src/jit-test/tests/ion/bug912152.js | Success (code 0, args "")
TEST-PASS | js/src/jit-test/tests/ion/bug912152.js | Success (code 0, args "--ion-eager --ion-offthread-compile=off")
TEST-PASS | js/src/jit-test/tests/ion/bug912152.js | Success (code 0, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --no-sse3 --no-threads")
TEST-PASS | js/src/jit-test/tests/ion/bug912152.js | Success (code 0, args "--baseline-eager")
TEST-PASS | js/src/jit-test/tests/ion/bug912152.js | Success (code 0, args "--baseline-eager --no-fpu")
TEST-PASS | js/src/jit-test/tests/ion/bug912152.js | Success (code 0, args "--no-baseline --no-ion")
TEST-PASS | js/src/jit-test/tests/ion/bug913749.js | Success (code 0, args "")
TEST-PASS | js/src/jit-test/tests/ion/bug913749.js | Success (code 0, args "--baseline-eager")
/builds/slave/m-in_l64-d_sm-ggc-000000000000/src/js/src/jit-test/tests/ion/bug913749.js:18:1 Error: Assertion failed: got "y.length is undefined", expected "y is undefined"
Exit code: 3
FAIL - ion/bug913749.js
TEST-UNEXPECTED-FAIL | js/src/jit-test/tests/ion/bug913749.js | /builds/slave/m-in_l64-d_sm-ggc-000000000000/src/js/src/jit-test/tests/ion/bug913749.js:18:1 Error: Assertion failed: got "y.length is undefined", expected "y is undefined" (code 3, args "--ion-eager --ion-offthread-compile=off")
INFO exit-status : 3
INFO timed-out : False
INFO stderr 2> /builds/slave/m-in_l64-d_sm-ggc-000000000000/src/js/src/jit-test/tests/ion/bug913749.js:18:1 Error: Assertion failed: got "y.length is undefined", expected "y is undefined"
/builds/slave/m-in_l64-d_sm-ggc-000000000000/src/js/src/jit-test/tests/ion/bug913749.js:18:1 Error: Assertion failed: got "y.length is undefined", expected "y is undefined"
Exit code: 3
FAIL - ion/bug913749.js
TEST-UNEXPECTED-FAIL | js/src/jit-test/tests/ion/bug913749.js | /builds/slave/m-in_l64-d_sm-ggc-000000000000/src/js/src/jit-test/tests/ion/bug913749.js:18:1 Error: Assertion failed: got "y.length is undefined", expected "y is undefined" (code 3, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --no-sse3 --no-threads")
INFO exit-status : 3
INFO timed-out : False
INFO stderr 2> /builds/slave/m-in_l64-d_sm-ggc-000000000000/src/js/src/jit-test/tests/ion/bug913749.js:18:1 Error: Assertion failed: got "y.length is undefined", expected "y is undefined"
TEST-PASS | js/src/jit-test/tests/ion/bug913749.js | Success (code 0, args "--baseline-eager --no-fpu")
TEST-PASS | js/src/jit-test/tests/ion/bug914098.js | Success (code 3, args "")
TEST-PASS | js/src/jit-test/tests/ion/bug913749.js | Success (code 0, args "--no-baseline --no-ion")
TEST-PASS | js/src/jit-test/tests/ion/bug914098.js | Success (code 3, args "--ion-eager --ion-offthread-compile=off")
TEST-PASS | js/src/jit-test/tests/ion/bug914098.js | Success (code 3, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --no-sse3 --no-threads")
TEST-PASS | js/src/jit-test/tests/ion/bug914098.js | Success (code 3, args "--baseline-eager")
TEST-PASS | js/src/jit-test/tests/ion/bug914098.js | Success (code 3, args "--baseline-eager --no-fpu")
TEST-PASS | js/src/jit-test/tests/ion/bug914098.js | Success (code 3, args "--no-baseline --no-ion")
TEST-PASS | js/src/jit-test/tests/ion/bug914341.js | Success (code 0, args "")
TEST-PASS | js/src/jit-test/tests/ion/bug914341.js | Success (code 0, args "--baseline-eager")
TEST-PASS | js/src/jit-test/tests/ion/bug914341.js | Success (code 0, args "--ion-eager --ion-offthread-compile=off")
TEST-PASS | js/src/jit-test/tests/ion/bug914341.js | Success (code 0, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --no-sse3 --no-threads")
TEST-PASS | js/src/jit-test/tests/ion/bug914341.js | Success (code 0, args "--baseline-eager --no-fpu")
TEST-PASS | js/src/jit-test/tests/ion/bug914341.js | Success (code 0, args "--no-baseline --no-ion")
TEST-PASS | js/src/jit-test/tests/ion/bug915301.js | Success (code 0, args "")
TEST-PASS | js/src/jit-test/tests/ion/bug915301.js | Success (code 0, args "--ion-eager --ion-offthread-compile=off")
TEST-PASS | js/src/jit-test/tests/ion/bug915301.js | Success (code 0, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --no-sse3 --no-threads")
TEST-PASS | js/src/jit-test/tests/ion/bug915301.js | Success (code 0, args "--baseline-eager")
TEST-PASS | js/src/jit-test/tests/ion/bug915301.js | Success (code 0, args "--baseline-eager --no-fpu")
Reporter

Updated

4 years ago
Summary: Frequent but intermittent → Frequent but intermittent bug913749.js:18:1 Error: Assertion failed: got "y.length is undefined", expected "y is undefined"
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Reporter

Comment 9

4 years ago
Terrence, any chance bug 1130226 could have caused this? It's near the top of the merge to b2g-inbound.
Flags: needinfo?(terrence)
None. The js length property works at a whole different level than the GC. Maybe Jason knows?
Flags: needinfo?(terrence) → needinfo?(jorendorff)
This isn't a bug with the length property: it's an error message bug. This kind of impossibly-bad error message typically means we're passing JSDVG_SEARCH_STACK to DecompileValueGenerator.

Why do we even have this lever?

Options:

0. Weaken the test and let the busted status quo continue.

1. Rip out JSDVG_SEARCH_STACK and severely curtail use of DecompileValueGenerator. Add more tests.

2. Remove the decompiler altogether. This would be a little sad because we would then have "undefined is not a function" error messages like everyone else.

I couldn't in good faith turn away a patch for any of these.

Orthogonally, we should add information about the relevant run-time values to the error message.
Flags: needinfo?(jorendorff)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
[Mass Closure] Closing bug as the WORKSFORME as the intermittent failure has not been seen for 45+ days If this has been closed and you feel that it should Not have been closed, please reopen and add [leave open] to the whiteboard.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.