[meta] Ensure all performance tests produce a perfherder-data.json artifact
Categories
(Testing :: Performance, task, P2)
Tracking
(Not tracked)
People
(Reporter: sparky, Assigned: myeongjun.ko)
References
Details
(Keywords: meta, Whiteboard: [fxp][operational])
Attachments
(1 obsolete file)
We'll need to start using the perfherder-data.json artifacts for parsing performance data from our Taskcluster tasks. To do this, all of our performance tests (mozperftest/awsy/raptor/talos/firefox-ios) will need to output a JSON file artifact called perfherder-data.json by default.
| Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
We'll have to double check every perftest to see what is missing it. From grooming we quickly checked on CI it seems many already have it, so we need to find the ones don't
Comment 2•1 year ago
|
||
Based on what the current investigations, the following mozperftest clearly do not produce a perfherder-data.json artifact:
- various mozperftest tasks containing "startup" in the name
- startup-fenix-cmff
- startup-fenix-cvns
- startup-geckoview-cmff
- startup-geckoview-cmff
- startup-chrome-m-cmff
- source-test-python-mozperftest
- various fetch_content jobs
- source-test-python-mozversioncontrol
Comment 3•1 year ago
|
||
We should probably create a separate ticket for adding perfherder-data.json file generation for all of the jobs mentioned.
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 4•1 year ago
|
||
To add to the list that :afinder produced, there are also build tasks that need to generate JSON files. This searchfox search should provide all of the areas that need to be checked to ensure that the perfherder-data is being output to a JSON file into the artifact folder: https://searchfox.org/firefox-main/search?q=PERFHERDER_DATA&path=&case=true®exp=false
Something to note is that some tasks will produce multiple perfherder-data entries. We will need to ensure that we append something to their name to ensure that they are unique. In terms of ingestion, on the treeherder side we could then parse the data from any JSON files that begin with or contain perfherder-data in the file name.
| Assignee | ||
Comment 5•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
| Reporter | ||
Comment 6•9 months ago
|
||
Closing this one as a duplicate of bug 1986824.
Updated•7 months ago
|
Updated•7 months ago
|
Description
•