Closed Bug 1869517 Opened 2 years ago Closed 2 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT /wasm/webapi/invalid-code.any.serviceworker.html | single tracking bug

Categories

(Core :: JavaScript: WebAssembly, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, intermittent-testcase)

Filed by: ncsoregi [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=439775501&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/N_btLgLDRquHKn1UyFyeqw/runs/0/artifacts/public/logs/live_backing.log


[task 2023-12-12T11:32:30.853Z] 11:32:30     INFO - TEST-START | /wasm/webapi/invalid-code.any.serviceworker.html
[task 2023-12-12T11:32:30.864Z] 11:32:30     INFO - Closing window 42829626-b0b6-4977-a901-a87023d4c927
[task 2023-12-12T11:33:05.858Z] 11:33:05     INFO - Got timeout in harness
[task 2023-12-12T11:33:05.860Z] 11:33:05     INFO - TEST-UNEXPECTED-TIMEOUT | /wasm/webapi/invalid-code.any.serviceworker.html | TestRunner hit external timeout (this may indicate a hang)
[task 2023-12-12T11:33:05.860Z] 11:33:05     INFO - TEST-INFO took 35008ms
[task 2023-12-12T11:34:18.347Z] 11:34:18     INFO - Browser exited with return code 572
[task 2023-12-12T11:34:18.372Z] 11:34:18     INFO - IOError on command, setting status to CRASH
[task 2023-12-12T11:34:18.373Z] 11:34:18     INFO - Browser not responding, setting status to CRASH
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.