After running a raptor test in CI, I have no idea how to trigger a Gecko Profile
Categories
(Testing :: Raptor, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: gregtatum, Unassigned)
References
Details
In Bug 1846806 I have really nice before and after links to Gecko profiles. After that, I have no idea how to trigger more Gecko Profiles with my actual code changes. For instance, I pushed up some changes here: https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&revision=e1b2919f75c18d0588af467eae44373c3554bdfe
I even tried to go through the flow of trigger gecko profiles, and it didn't work.
|
||
Comment 1•2 years ago
•
|
||
:gregtatum from the query selected there are just the unit tests for raptor
to select more you would have to query browsertime among a few other things. I will file a bug to modify documentation to make that more clear
you can also try using mach try perf https://firefox-source-docs.mozilla.org/testing/perfdocs/mach-try-perf.html
but with fuzzy maybe a query like -q "'browsertime 'shipp '64 'essential 'firefox"
or to target the specific sites in the regression "'browsertime 'firefox 'tp6 'google-search | 'twitch | ... and so on
the 'essential query targets any subtest as part of tp6 essential, so you can omit it for tests outside of the essential set (e.g.)
Anyhow, these tests have --extra-profiler-run enabled by default in CI and you can see it in the artifacts after. Maybe that will be enough of a profile?
|
Reporter | |
Comment 2•2 years ago
|
||
Thanks, that's really good information. I would recommend putting the information on the top result for a google search: site:firefox-source-docs.mozilla.org raptor, which is https://firefox-source-docs.mozilla.org/testing/perfdocs/raptor.html
This has a command to run it locally, so understanding how to push to try seems like a place where it's easy to find.
|
|
||
Comment 3•2 years ago
|
||
I will close this for now and track the doc work in Bug 1847782
Description
•