Closed
Bug 1632862
Opened 5 years ago
Closed 5 years ago
XPCShell tests should have profiler markers to show what's happening
Categories
(Testing :: XPCShell Harness, task)
Tracking
(firefox78 fixed)
RESOLVED
FIXED
mozilla78
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: florian, Assigned: florian)
References
Details
Attachments
(1 file)
Similar to what I'm doing in bug 1630971, I think xpcshell test profiles should be easy to read, and adding markers showing which code and which part of the test is executed should go a long way.
|
Assignee | |
Comment 1•5 years ago
|
||
|
|
Assignee | |
Comment 2•5 years ago
|
||
Example profile: https://perfht.ml/2S6Jmk9 This is captured locally using MOZ_PROFILER_STARTUP=1 MOZ_PROFILER_SHUTDOWN=<filename> ./mach ....
On try, one can capture xpcshell profiles using https://hg.mozilla.org/try/rev/5e1e59358908db7252c526d7f676247372c80d41
Pushed by fqueze@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6be1d85b0da4
Add profiler markers in xpcshell tests, r=gbrown.
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox78:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in
before you can comment on or make changes to this bug.
Description
•