Intermittent GeckoProfiler.CPUUsage | Expected: (threadCPUDeltaZeroCount) > (threadCPUDeltaNonZeroCount), actual: 7 vs 14
Categories
(Core :: Gecko Profiler, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox94 | --- | unaffected |
| firefox95 | --- | unaffected |
| firefox96 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: mozbugz)
References
(Regression)
Details
(Keywords: intermittent-failure, regression)
Attachments
(1 file)
Filed by: nbeleuzu [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=357672284&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/PFSEp0dBS1WfWLvIR0THrQ/runs/0/artifacts/public/logs/live_backing.log
[task 2021-11-10T19:42:42.944Z] 19:42:42 INFO - TEST-START | GeckoProfiler.CPUUsage
[task 2021-11-10T19:42:43.027Z] 19:42:43 WARNING - TEST-UNEXPECTED-FAIL | GeckoProfiler.CPUUsage | Expected: (threadCPUDeltaZeroCount) > (threadCPUDeltaNonZeroCount), actual: 7 vs 14
[task 2021-11-10T19:42:43.030Z] 19:42:43 INFO - There should be more zero-CPUs than non-zero @ /builds/worker/checkouts/gecko/tools/profiler/tests/gtest/GeckoProfiler.cpp:4304
[task 2021-11-10T19:42:43.121Z] 19:42:43 WARNING - TEST-UNEXPECTED-FAIL | GeckoProfiler.CPUUsage | test completed (time: 178ms)
| Assignee | ||
Comment 1•4 years ago
|
||
As feared, the test needs tweaking -- But the Firefox code is not at cause here, so no need to backout.
NI:myself, I will wait a few days to collect more test failures, which will give us more information to better adjust the test expectations.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Set release status flags based on info from the regressing bug 1736616
| Assignee | ||
Comment 3•4 years ago
|
||
The expectation of 50% idle stacks was too optimistic, since we cannot control how the OS interact with idle threads and may still had CPU time to them unexpectedly.
The patch now only expects at least one zero and at least one non-zero.
The non-zero should be guaranteed by the work necessary to go around the loop.
The zero is still hopeful, in practice we've seen a minimum of 7 (out of 20) zeroes. But in the worst case it could still theoretically fail; If that happens we may need to increase the loop count, or try the whole test a few times.
Updated•4 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Updated•4 years ago
|
Comment 6•4 years ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
Description
•