Fix mozproxy-replay perfherder data names.
Categories
(Testing :: Raptor, defect, P2)
Tracking
(firefox78 fixed)
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: sparky, Assigned: sparky)
Details
Attachments
(1 file)
This bug is for fixing the mozproxy names in the perfherder data output since they have a lot of redundancy.
The name of the subtests should change from:
name: "mozproxy-replay-confidence"
to:
name: "confidence"
This change will need to be specific to only mozproxy data because the power data still has the redundancy and is being used by dashboards (so we will need to fix the dashboards at the same time - we will do this change when we go from raptor to browsertime).
|
||
Comment 1•4 years ago
|
||
And include the measurement in the test perfherder data
ex:
as a subtest like we have fcp, load time
|
Assignee | |
Comment 2•4 years ago
|
||
This patch reduces the redundancy in the mozproxy perfherder data names. It removes the replay suffix since it's already clear it's related to replay/not-replayed. The subtest names have the mozproxy-replay prefix removed through the addition of a new way of specifying supporting measurement values. Instead of only being able to submit the values with a {measurement: values} format, we can now submit it as {measurement: {values: [], concat: False}}. The concat field will determine if the type and measurement name fields should be concatenated.
|
||
Updated•4 years ago
|
Pushed by gmierz2@outlook.com: https://hg.mozilla.org/integration/autoland/rev/c36b691002dd Remove redundancy from mozproxy perfherder data names. r=perftest-reviewers,AlexandruIonescu,Bebe,davehunt
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Description
•