Closed
Bug 1609402
Opened 4 years ago
Closed 4 years ago
jit-test/tests/gc/bug-1505622.js fails on arm64-sim on a sufficiently busy system
Categories
(Core :: JavaScript: GC, defect, P2)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
mozilla74
Tracking | Status | |
---|---|---|
firefox74 | --- | fixed |
People
(Reporter: lth, Assigned: jonco)
Details
Attachments
(1 file)
Linux, --enable-debug --disable-optimize --without-intl-api --enable-simulator=arm64:
$ ../jit-test/jit_test.py dist/bin/js gc/bug-1
[176| 0| 0| 0] 91% =========================================> | 79.5s
/home/lhansen/m-c/js/src/jit-test/tests/gc/bug-1505622.js:38:9 Error: Assertion failed: got 1, expected 0
Stack:
@/home/lhansen/m-c/js/src/jit-test/tests/gc/bug-1505622.js:38:9
Exit code: 3
FAIL - gc/bug-1505622.js
[192| 1| 0| 0] 100% ==============================================>| 199.0s
FAILURES:
gc/bug-1505622.js
TIMEOUTS:
$ ../jit-test/jit_test.py dist/bin/js gc/bug-1505
[1|0|0|0] 100% ==========================================================>| 15.6s
PASSED ALL
So far as I can tell, it is completely consistent: running the test alone, it never fails. Running it with a bunch of other tests, and it fails reliably.
Assignee | ||
Updated•4 years ago
|
Assignee: nobody → jcoppeard
Priority: -- → P2
Assignee | ||
Comment 1•4 years ago
|
||
Tests that involve timing are often problematic. Here we're checking that hitting the heap limit inside the five second time limit we set for skipping last ditch GCs doesn't trigger a GC, but allocating enough to hit this limit can take longer than five seconds on a busy system.
The patch makes the max heap size much smaller and so reduces the possibility that that this can happen.
Pushed by jcoppeard@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/86c17304b4ad Improve flakey test that relied on being able to allocate 1MB of GC things in under 5 seconds r=sfink
Comment 3•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in
before you can comment on or make changes to this bug.
Description
•