windows/aarch64 - tests\jit-test\jit-test\tests\self-test\assertRecoveredOnBailout-1.js | Hit MOZ_CRASH(Cannot test assertRecoveredOnBailout) at z:/build/build/src/js/src/shell/js.cpp:3695 (code -1073741795, args "") [0.2 s]
Categories
(Core :: JavaScript Engine, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: nbp)
References
Details
(Keywords: regression)
Attachments
(1 file)
#[markdown(off)]
Filed by: egao [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=230809597&repo=try
Observed during windows10-aarch64/opt-jittest.
Context:
18:06:48 WARNING - TEST-UNEXPECTED-FAIL | tests\jit-test\jit-test\tests\self-test\assertRecoveredOnBailout-1.js | Hit MOZ_CRASH(Cannot test assertRecoveredOnBailout) at z:/build/build/src/js/src/shell/js.cpp:3695 (code -1073741795, args "") [0.2 s]
18:06:48 INFO - {"action": "test_start", "jitflags": "", "pid": 9692, "source": "jittests", "test": "self-test\\assertRecoveredOnBailout-1.js", "thread": "main", "time": 1551290807.819}
18:06:48 INFO - {"action": "test_end", "extra": {"jitflags": ""}, "jitflags": "", "message": "Hit MOZ_CRASH(Cannot test assertRecoveredOnBailout) at z:/build/build/src/js/src/shell/js.cpp:3695", "pid": 9692, "source": "jittests", "status": "FAIL", "test": "self-test\\assertRecoveredOnBailout-1.js", "thread": "main", "time": 1551290808.047}
18:06:48 INFO - INFO exit-status : -1073741795
18:06:48 INFO - INFO timed-out : False
18:06:48 INFO - INFO stderr 2> Hit MOZ_CRASH(Cannot test assertRecoveredOnBailout) at z:/build/build/src/js/src/shell/js.cpp:3695
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
![]() |
||
Comment 3•6 years ago
|
||
I confirmed that this is still easily reproducible today:
If this test is skipped, the windows/aarch64 jittest task is green more often than not:
Comment hidden (Intermittent Failures Robot) |
Comment 5•6 years ago
|
||
I can't reproduce it, but I'll take a look. It's crashing in test setup code that doesn't use jitcode yet.
Assignee | ||
Comment 6•6 years ago
|
||
From my point of view, the issue is in the test harness, which does not interpret a an expected crashing test as an expected case. Not in the test case, which is crashing as expected.
My blind guess would be to look around the remote worker if any, or around this handling of the error code:
https://searchfox.org/mozilla-central/source/js/src/tests/lib/jittests.py#498-514
My guess would be that we need to add the following case:
if sys.platform == 'win32' and rc == 29 - 2 ** 30: return True
and maybe insert a test for Aarch64.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 7•4 years ago
|
||
Updated•4 years ago
|
Comment 9•4 years ago
|
||
bugherder |
Description
•