Open
Bug 1892260
Opened 1 year ago
Updated 6 months ago
[meta] Ensure all performance tests produce a perfherder-data.json artifact
Categories
(Testing :: Performance, task, P2)
Testing
Performance
Tracking
(Not tracked)
NEW
People
(Reporter: sparky, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [fxp])
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•1 year ago
|
Whiteboard: [fxp]
Updated•1 year ago
|
Comment 1•1 year 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•6 months 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•6 months ago
|
||
We should probably create a separate ticket for adding perfherder-data.json file generation for all of the jobs mentioned.
Reporter | ||
Updated•6 months ago
|
Summary: Ensure all performance tests produce a perfherder-data.json artifact → [meta] Ensure all performance tests produce a perfherder-data.json artifact
You need to log in
before you can comment on or make changes to this bug.
Description
•