gecko-dev/testing/runtimes
Dan Minor d296a671f5 Bug 1264772 - Fixup writeruntimes.py; r=ahal
This fixes a few typos in the script and updates the README with
instructions on how to run it.

MozReview-Commit-ID: 7XVgTIFZR2M

--HG--
extra : rebase_source : 3d5c3101824d77735afef966e5f90013c4cefaae
2016-04-14 16:01:14 -04:00
..
mochitest-browser-chrome.runtimes.json Bug 1199241 - Average runtime data across platforms instead of keeping it distinct, r=jgriffin 2015-08-27 17:37:26 -04:00
mochitest-devtools-chrome.runtimes.json Bug 912121 - Update misc. DevTools paths and comments. rs=devtools 2015-09-21 12:07:31 -05:00
mochitest-e10s-browser-chrome.runtimes.json Bug 1199241 - Average runtime data across platforms instead of keeping it distinct, r=jgriffin 2015-08-27 17:37:26 -04:00
mochitest-e10s-devtools-chrome.runtimes.json Bug 912121 - Update misc. DevTools paths and comments. rs=devtools 2015-09-21 12:07:31 -05:00
moz.build
README.md Bug 1264772 - Fixup writeruntimes.py; r=ahal 2016-04-14 16:01:14 -04:00
writeruntimes.py Bug 1264772 - Fixup writeruntimes.py; r=ahal 2016-04-14 16:01:14 -04:00

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