Use consistent fission perfherder data naming for talos/raptor/awsy
Categories
(Testing :: Performance, enhancement, P1)
Tracking
(firefox73 verified)
| Tracking | Status | |
|---|---|---|
| firefox73 | --- | verified |
People
(Reporter: rwood, Assigned: rwood)
Details
Attachments
(1 file, 1 obsolete file)
As Chris noted, we are using different fission labels for perfherder data ('extraOptions') for talos/raptor/awsy:
- Talos tests are labeled
fission:
- Raptor tests are labeled
fission_enabled(with an underscore):
- AWSY tests labeled
fission-enabled(with a hyphen):
Let's use the same fission label for all the frameworks for perfherder.
| Assignee | ||
Comment 1•6 years ago
|
||
I would suggest we just use "fission", if everyone agrees? That will make the perfherder graph labels shorter too.
I'm sold on "fission"; thanks!
| Assignee | ||
Comment 4•6 years ago
|
||
| Assignee | ||
Comment 5•6 years ago
|
||
Oops attached patch to wrong bug; please disregard
Updated•6 years ago
|
| Assignee | ||
Comment 6•6 years ago
|
||
| Assignee | ||
Comment 7•6 years ago
|
||
| Assignee | ||
Comment 8•6 years ago
|
||
Updated patch with a fix for a non-related / pre-existing intermittent raptor unit test failure:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=59f83f66c65a27e3e822dba6b20ccdea09994208
| Assignee | ||
Comment 9•6 years ago
|
||
And just with the update for the lint fix:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=85b64c7cefdc7d8dda89a5ddd7795a9cca113c89
| Assignee | ||
Comment 10•6 years ago
|
||
(In reply to Robert Wood [:rwood] from comment #7)
Looks good!
Raptor:
INFO - perftest-output Info: PERFHERDER_DATA: {"framework": {"name": "raptor"}, "application": {"version": "73.0a1", "name": "firefox"}, "suites": [{"value": 78.82673856314936, "extraOptions": ["fission"],
Talos:
INFO - PERFHERDER_DATA: {"framework": {"name": "talos"}, "suites": [{"extraOptions": ["e10s", "stylo", "fission"],
AWSY:
INFO - PERFHERDER_DATA: {"framework": {"name": "awsy"}, "suites": [{"extraOptions": ["tp6", "fission", "stylo"],
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
| bugherder | ||
Comment 13•6 years ago
|
||
(In reply to Robert Wood [:rwood] from comment #1)
I would suggest we just use "fission", if everyone agrees? That will make the perfherder graph labels shorter too.
"fission" SGTM. Thanks!
(In reply to Pulsebot from comment #11)
Pushed by rwood@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0a1d7fd259a6
Use consistent fission perfherder data naming for talos/raptor/awsy
Rob, is this GeckoView change to testing/raptor/test/test_cpu.py needed to fix the Fission test names? I don't know this code, but the change seems unrelated.
def test_no_device():
- raptor = RaptorAndroid('geckoview', 'org.mozilla.org.mozilla.geckoview_example', cpu_test=True)
+ raptor = RaptorAndroid('geckoview', 'org.mozilla.org.mozilla.geckoview_example',
+ cpu_test=True, no_conditioned_profile=False)
| Assignee | ||
Comment 14•6 years ago
|
||
(In reply to Chris Peterson [:cpeterson] (PTO: December 24 – January 1) from comment #13)
Rob, is this GeckoView change to testing/raptor/test/test_cpu.py needed to fix the Fission test names? I don't know this code, but the change seems unrelated.
Yes it was unrelated but it fixed an intermittent raptor unit test failure that appeared in my try push; see Comment 8.
(In reply to Robert Wood [:rwood] from comment #8)
Updated patch with a fix for a non-related / pre-existing intermittent raptor unit test failure:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=59f83f66c65a27e3e822dba6b20ccdea09994208
👍
Comment 16•6 years ago
|
||
Thanks! I see the new "fission" test names in Perfherder now.
Description
•