Closed Bug 1802772 Opened 3 years ago Closed 2 years ago

Intermittent [tier 2] /css/css-lists/crashtests/chrome-counter-in-multicol-details-crash.html | single tracking bug

Categories

(Core :: Layout: Generated Content, Lists, and Counters, defect, P5)

Product:
Core
Component:
Layout: Generated Content, Lists, and Counters
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, intermittent-testcase)

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

[task 2022-11-27T10:42:24.937Z] 10:42:24     INFO - TEST-START | /css/css-lists/crashtests/chrome-counter-in-multicol-details-crash.html
[task 2022-11-27T10:42:24.955Z] 10:42:24     INFO - Setting pref dom.animations-api.compositing.enabled to true
[task 2022-11-27T10:42:24.974Z] 10:42:24     INFO - Setting pref layout.css.cascade-layers.enabled to true
[task 2022-11-27T10:42:59.939Z] 10:42:59     INFO - Got timeout in harness
[task 2022-11-27T10:42:59.941Z] 10:42:59     INFO - TEST-UNEXPECTED-TIMEOUT | /css/css-lists/crashtests/chrome-counter-in-multicol-details-crash.html | TestRunner hit external timeout (this may indicate a hang)
[task 2022-11-27T10:42:59.941Z] 10:42:59     INFO - TEST-INFO took 35003ms
[task 2022-11-27T10:44:11.015Z] 10:44:11     INFO - Browser exited with return code -15
[task 2022-11-27T10:44:11.071Z] 10:44:11     INFO - IOError on command, setting status to CRASH
[task 2022-11-27T10:44:11.071Z] 10:44:11     INFO - Browser not responding, setting status to CRASH
[task 2022-11-27T10:44:11.072Z] 10:44:11  WARNING - Command left in command_queue during cleanup: 'test_ended', (<wptrunner.wpttest.CrashTest /css/css-lists/crashtests/chrome-counter-in-multicol-details-crash.html>, (<wptrunner.wpttest.CrashtestResult CRASH>, []))
[task 2022-11-27T10:44:11.072Z] 10:44:11     INFO - Closing logging queue
[task 2022-11-27T10:44:11.073Z] 10:44:11     INFO - queue closed
[task 2022-11-27T10:44:11.089Z] 10:44:11     INFO - Application command: /builds/worker/workspace/build/application/firefox/firefox --marionette about:blank -profile /tmp/tmpl6gpxc1s
[task 2022-11-27T10:44:11.127Z] 10:44:11     INFO - PID 11408 | [CodeCoverage] Setting handlers for process 11408.
[task 2022-11-27T10:44:11.128Z] 10:44:11     INFO - PID 11408 | 1669545745311	Marionette	INFO	Marionette enabled
[task 2022-11-27T10:44:11.129Z] 10:44:11     INFO - PID 11408 | 1669545745315	Marionette	INFO	Listening on port 56490
[task 2022-11-27T10:44:11.129Z] 10:44:11     INFO - PID 11408 | console.warn: SearchSettings: "get: No settings file exists, new profile?" (new NotFoundError("Could not open the file at /tmp/tmpqp3_yicw/search.json.mozlz4", (void 0)))
[task 2022-11-27T10:44:11.129Z] 10:44:11     INFO - PID 11408 | ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
[task 2022-11-27T10:44:11.129Z] 10:44:11     INFO - Starting runner
[task 2022-11-27T10:44:11.932Z] 10:44:11     INFO - PID 11408 | [CodeCoverage] Setting handlers for process 11510.
[task 2022-11-27T10:44:12.234Z] 10:44:12     INFO - PID 11408 | [CodeCoverage] Setting handlers for process 11506.
[task 2022-11-27T10:44:12.502Z] 10:44:12     INFO - TEST-START | /css/css-lists/crashtests/chrome-legacy-propagation-crash.html

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit auto_nag documentation.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE

New failure instance: https://treeherder.mozilla.org/logviewer?job_id=438629917&repo=try

Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

Status: REOPENED → RESOLVED
Closed: 3 years ago → 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.