gecko-dev/tools/profiler/tests
Gerald Squelart a811180396 Bug 1664732 - Transition DOMEvent to markers 2.0 - r=gregtatum,smaug
There is only one call site, so I believe it's best to have the marker type there.
I think it's cleaner this way, this marker type doesn't need to be present in a header shared by all users of the profiler.

The only downside is that we cannot unit-test this particular marker type automatically anymore, but I don't think it's strictly needed:
- There are still plenty of tests checking that generic marker types work end-to-end, so we can have some confidence this specific one can do its job.
- If it somehow started to fail, either it would be quickly found that it breaks the front-end, or it wouldn't have any visible effect in which case it's not a big issue.
Follow-up bug 1665810 will instead add a higher-level xpcshell test or mochitest.

Differential Revision: https://phabricator.services.mozilla.com/D90185
2020-09-18 01:46:48 +00:00
..
browser Bug 1589568 - Add some more logs in an intermittent profiler test r=gregtatum 2020-05-05 14:57:45 +00:00
chrome
gtest Bug 1664732 - Transition DOMEvent to markers 2.0 - r=gregtatum,smaug 2020-09-18 01:46:48 +00:00
xpcshell Bug 1650068 - Enable profiler tests r=JuniorHsu 2020-07-02 15:25:44 +00:00
shared-head.js Bug 1648507 - Distinguish pausing sampling only from pausing the whole profiler - r=canaltinova,perftest-reviewers,geckoview-reviewers,agi 2020-07-02 01:36:27 +00:00