Intermittent toolkit/components/processtools/tests/browser/browser_test_powerMetrics.js | no CPU time should be recorded in the __other__ label - 84 === null -
Categories
(Toolkit :: Performance Monitoring, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: gerard-majax)
References
Details
(Keywords: intermittent-failure, test-verify-fail)
Attachments
(1 file)
Filed by: alissy [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=463326218&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CyP5CbNBR3e4ls30b0_4GQ/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CyP5CbNBR3e4ls30b0_4GQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
`mach try fuzzy --rebuild 20 -q "'linux" toolkit/components/processtools/tests/browser/browser_test_powerMetrics.js`
Assignee | ||
Comment 1•5 months ago
•
|
||
Appears when i test bug 1896054 but it might have been here before
Assignee | ||
Comment 2•5 months ago
|
||
ok, so when investigated i did a mistake which confirms bug 1896054 is unrelated: https://hg.mozilla.org/try/pushloghtml?changeset=f3902038153071b60d8f8a1ec902ea83b2456097 this repro and is with the XDG changes ... https://treeherder.mozilla.org/jobs?repo=try&author=alissy%40mozilla.com&selectedTaskRun=ag6UjgZ0S76UxcGiLMVT2w.0
Assignee | ||
Comment 3•5 months ago
|
||
And from https://treeherder.mozilla.org/jobs?repo=try&revision=c3cd766bb21b56a86f95c5c900bb49002f357960 i can't prove a higher level of intermittence due to bug 1896054
Assignee | ||
Comment 4•5 months ago
|
||
Updated•5 months ago
|
Comment hidden (Intermittent Failures Robot) |
Updated•5 months ago
|
Comment 6•5 months ago
|
||
Looking at the history of failures in bug 1819845, it seems this failure has been stared 6 times, only on test-verify jobs, so there's likely a race condition that fails only in chaos mode.
Comment 8•5 months ago
|
||
bugherder |
Description
•