gecko-dev/testing/runtimes
Blake Kaplan 3fa965430b Bug 1406212 - Remove references to extensions.e10sBlocksEnabling. r=Felipe
MozReview-Commit-ID: 11q3Go0IkPh

--HG--
extra : rebase_source : fdcf714d18effc964191665eb8422305bda92b65
2017-10-16 13:52:48 -07:00
..
README.md
mochitest-browser-chrome-e10s.runtimes.json Bug 1406212 - Remove references to extensions.e10sBlocksEnabling. r=Felipe 2017-10-16 13:52:48 -07:00
mochitest-browser-chrome.runtimes.json
mochitest-devtools-chrome-e10s.runtimes.json
mochitest-devtools-chrome.runtimes.json
mochitest-media-e10s.runtimes.json
mochitest-media.runtimes.json
moz.build
writeruntimes.py

README.md

Test Runtimes

These files contain test runtimes for various suites across different platforms. Each JSON file corresponds to a single test job in production and has the following format:

{ '<test id>': <average runtime> }

These files are being used to normalize chunk durations so all chunks take roughly the same length of time. They are still experimental and their format and/or file structure are subject to change without notice.

Generating a Test Runtime File

The writeruntimes.py script can be used to generate a runtime file. You must specify the suite for which the runtimes are to be generated, e.g.

writeruntimes.py -s mochitest-media