gecko-dev/testing/runtimes
Andrew Halberstadt d93619e0ad Bug 1324047 - Update test runtimes data files, r=jgriffin
MozReview-Commit-ID: HuDOVFDQOmk

--HG--
extra : rebase_source : 80661fceed7ab19f67b70b039824db02c3842f8e
2016-12-19 12:10:39 -05:00
..
README.md
mochitest-browser-chrome-e10s.runtimes.json Bug 1324047 - Update test runtimes data files, r=jgriffin 2016-12-19 12:10:39 -05:00
mochitest-browser-chrome.runtimes.json Bug 1324047 - Update test runtimes data files, r=jgriffin 2016-12-19 12:10:39 -05:00
mochitest-devtools-chrome-e10s.runtimes.json Bug 1324047 - Update test runtimes data files, r=jgriffin 2016-12-19 12:10:39 -05:00
mochitest-devtools-chrome.runtimes.json Bug 1324047 - Update test runtimes data files, r=jgriffin 2016-12-19 12:10:39 -05:00
mochitest-media-e10s.runtimes.json Bug 1324047 - Update test runtimes data files, r=jgriffin 2016-12-19 12:10:39 -05:00
mochitest-media.runtimes.json Bug 1324047 - Update test runtimes data files, r=jgriffin 2016-12-19 12:10:39 -05:00
moz.build
writeruntimes.py Bug 1324047 - Update testing/runtimes/writeruntimes.py for new e10s schema in ActiveData, r=jgriffin 2016-12-19 12:09:10 -05:00

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