Closed
Bug 1905760
Opened 10 months ago
Closed 9 months ago
Intermittent tests/jit-test/jit-test/tests/wasm/regress/oom-wrong-argument-number-for-import-call.js | Unknown (code -5, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --ion-extra-checks --no-sse3 --no-threads") [0.0 s]
Categories
(Core :: JavaScript Engine, defect, P5)
Core
JavaScript Engine
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure)
Filed by: imoraru [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=464746766&repo=mozilla-esr128
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/WdHX85N6RR-iI4_mZxs4tQ/runs/0/artifacts/public/logs/live_backing.log
[task 2024-07-01T19:31:06.780Z] 19:31:06 INFO - TEST-PASS | tests/jit-test/jit-test/tests/wasm/regress/oom-wrong-argument-number-for-import-call.js | Success (code 0, args "") [0.0 s]
[task 2024-07-01T19:31:06.781Z] 19:31:06 INFO - Exit code: -5
[task 2024-07-01T19:31:06.781Z] 19:31:06 INFO - FAIL - wasm/regress/oom-wrong-argument-number-for-import-call.js
[task 2024-07-01T19:31:06.781Z] 19:31:06 WARNING - TEST-UNEXPECTED-FAIL | tests/jit-test/jit-test/tests/wasm/regress/oom-wrong-argument-number-for-import-call.js | Unknown (code -5, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --ion-extra-checks --no-sse3 --no-threads") [0.0 s]
[task 2024-07-01T19:31:06.783Z] 19:31:06 INFO - INFO exit-status : -5
[task 2024-07-01T19:31:06.783Z] 19:31:06 INFO - INFO timed-out : False
[task 2024-07-01T19:31:06.792Z] 19:31:06 INFO - TEST-PASS | tests/jit-test/jit-test/tests/wasm/regress/oom-wrong-argument-number-for-import-call.js | Success (code 0, args "--baseline-eager --write-protect-code=off") [0.0 s]
Comment 1•9 months ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•