Closed Bug 1503380 Opened 3 years ago Closed 3 years ago
When running raptor gecko profiling jobs, raptor should still save results to a raptor
Bug 1503380 - When running raptor gecko profiling jobs, raptor should still save results to a raptor.json artifact; r?jmaher
47 bytes, text/x-phabricator-request
|Details | Review|
Currently when running Raptor in production with gecko profiling (--gecko-profile) turned on, we don't write the results to a .json artifact (since we don't dump out PERFHERDER_DATA formatted results when running with profiling as we don't want perfherder to ingest the measurements). We should still write the results for the 2 profiling pagecycles to a raptor.json anyway and have it saved as a taskcluster artifact, so that when developers are looking at the profiles they can also see the actual raw results. When running locally with --gecko-profile the results are available in /testing/mozharness/build/raptor.json - but such a .json is not available on production profiling runs.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/c06ea2a391cb When running raptor gecko profiling jobs, raptor should still save results to a raptor.json artifact; r=jmaher
You need to log in before you can comment on or make changes to this bug.