Closed
Bug 1656540
Opened 4 years ago
Closed 4 years ago
Subtest metric settings are not used when building perfherder data
Categories
(Testing :: mozperftest, defect, P1)
Testing
mozperftest
Tracking
(firefox81 fixed)
RESOLVED
FIXED
81 Branch
| Tracking | Status | |
|---|---|---|
| firefox81 | --- | fixed |
People
(Reporter: sparky, Assigned: sparky)
References
Details
Attachments
(1 file)
Currently, if you have a test called cloudflare but its metrics are named like name:firstPaint,extraOptions:["http3"] then the options will be ignored for the test but we should be able to specify these options on a per-metric basis. extraOptions is only available at the suite-level so all those specification should be merged.
|
Assignee | |
Comment 1•4 years ago
|
||
This patch fixes an issue where the metric settings were not being used because they don't use the test name. It also handles some changes (from a bad copy-paste) that didn't make it into the last live-site patch series.
Pushed by gmierz2@outlook.com: https://hg.mozilla.org/integration/autoland/rev/b307d3278c84 Allow specifying perfherder settings on a per-metric basis. r=tarek
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox81:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•