Closed
Bug 1743915
Opened 2 years ago
Closed 2 years ago
Intermittent GeckoProfiler.CPUUsage | Expected: (threadCPUDeltaNonZeroCount) > (0u), actual: 0 vs 0
Categories
(Core :: Gecko Profiler, defect, P3)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
96 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox94 | --- | unaffected |
| firefox95 | --- | unaffected |
| firefox96 | --- | fixed |
People
(Reporter: mozbugz, Assigned: mozbugz)
References
(Regression)
Details
(Keywords: intermittent-failure, regression)
Attachments
(1 file)
Yet another follow-up for this intermittent. Bug 1741355 didn't fix it. But hopefully it may help with lowering its frequency? Too early to judge.
Thoughts at the moment:
- This check is not strictly needed, and the test itself is not about detecting non-zero CPU values, so I could just get rid of it.
- I could better coordinate the test threads and the profiling, to ensure idle and non-idle time really happen while the main thread is doing the profiling.
|
Assignee | |
Updated•2 years ago
|
Keywords: intermittent-failure
|
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1736616
status-firefox94:
--- → unaffected
status-firefox95:
--- → unaffected
status-firefox96:
--- → affected
status-firefox-esr91:
--- → unaffected
Pushed by gsquelart@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e76a50569b20 GeckoProfiler.CPUUsage gtest: Add a thread that's busy all the time, to ensure non-zero CPU values during profiling - r=canaltinova
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
| Comment hidden (Intermittent Failures Robot) |
|
||
Updated•2 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•