83
edits
Changes
→xperf: Mention which platforms that xperf tests can be found on and provide a query for it.
* measuring: IO counters from windows (currently, only startup IO is in scope)
* reporting: Summary of read/write counters for disk, network (lower is better)
These tests only run on windows builds. See [https://activedata.allizom.org/tools/query.html#query_id=zqlX+2Jn this active-data query] for an updated set of platforms that xperf can be found on. If the query is not found, use the following on the query page:
<pre>
{
"from":"task",
"groupby":["run.name","build.platform"],
"limit":2000,
"where":{"regex":{"run.name":".*xperf.*"}}
}
</pre>
Talos will turn orange for 'x' jobs on windows 7 if your changeset accesses files which are not predefined in the [[https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/xtalos/xperf_whitelist.json whitelist]] during startup; specifically, before the "[https://hg.mozilla.org/mozilla-central/file/0eebc33d8593/toolkit/components/startup/nsAppStartup.cpp#l631 sessionstore-windows-restored]" Firefox event. If your job turns orange, you will see a list of files in Treeherder (or in the log file) which have been accessed unexpectedly (similar to this):
