Closed
Bug 1780238
Opened 2 years ago
Closed 2 years ago
Add an extra-option for the bytecode-cache tests
Categories
(Testing :: Raptor, defect, P1)
Testing
Raptor
Tracking
(firefox-esr91 unaffected, firefox-esr102 unaffected, firefox102 unaffected, firefox103 unaffected, firefox104 fixed)
RESOLVED
FIXED
104 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox-esr102 | --- | unaffected |
| firefox102 | --- | unaffected |
| firefox103 | --- | unaffected |
| firefox104 | --- | fixed |
People
(Reporter: sparky, Assigned: sparky)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Currently, our data for the bytecode-cache test is being mixed with the data from the non bytecode-cache tests. We need to add an extra option to distinguish the two results.
|
Assignee | |
Comment 1•2 years ago
|
||
This patch adds an extra option to the test when we run with --test-bytecode-cache. It also prevents it from getting added to chrome/chromium tests. This fixes an issue where the time series are currently being merged together.
|
||
Updated•2 years ago
|
Keywords: regression
|
|
||
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1779468
status-firefox102:
--- → unaffected
status-firefox103:
--- → unaffected
status-firefox104:
--- → affected
status-firefox-esr102:
--- → unaffected
status-firefox-esr91:
--- → unaffected
Pushed by gmierz2@outlook.com: https://hg.mozilla.org/integration/autoland/rev/8fbe31ba6472 Add extra option for byte-code cache tests. r=perftest-reviewers,kshampur
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•