Closed
Bug 1702689
Opened 3 years ago
Closed 3 years ago
Using more than one cycle in a benchmark test only outputs one cycle
Categories
(Testing :: Raptor, defect, P1)
Testing
Raptor
Tracking
(firefox-esr78 unaffected, firefox87 unaffected, firefox88 unaffected, firefox89 fixed)
RESOLVED
FIXED
89 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox87 | --- | unaffected |
| firefox88 | --- | unaffected |
| firefox89 | --- | fixed |
People
(Reporter: sparky, Assigned: alexandrui)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
The update being done here overwrites earlier cycles and this needs to be fixed: https://searchfox.org/mozilla-central/source/testing/raptor/raptor/results.py#561
|
||
Comment 1•3 years ago
|
||
Set release status flags based on info from the regressing bug 1690746
status-firefox87:
--- → unaffected
status-firefox88:
--- → unaffected
status-firefox89:
--- → affected
status-firefox-esr78:
--- → unaffected
|
Assignee | |
Updated•3 years ago
|
Assignee: nobody → aionescu
Status: NEW → ASSIGNED
Priority: P2 → P1
|
|
Assignee | |
Comment 2•3 years ago
|
||
|
|
||
Updated•3 years ago
|
Keywords: regression
|
||
Updated•3 years ago
|
Attachment #9213324 -
Attachment description: Bug 1702689 Using more than one cycle in a benchmark test only outputs one cycle r=#perftest → Bug 1702689 Fix browsertime_benchmark.js collect all pagecycle results r=#perftest
|
|
||
Updated•3 years ago
|
Attachment #9213324 -
Attachment description: Bug 1702689 Fix browsertime_benchmark.js collect all pagecycle results r=#perftest → Bug 1702689 - Fix browsertime_benchmark.js to collect all pagecycle results r=#perftest
Pushed by aionescu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6c03f84fe379 Fix browsertime_benchmark.js to collect all pagecycle results r=perftest-reviewers,sparky
|
||
Comment 4•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•