gecko-dev/testing/runtimes
Andrew Halberstadt 1e8f0b0dac Bug 1600314 - [runtimes] Don't store runtime information for included manifests, r=gbrown
Some manifests get included by parent manifests (e.g [include:<child
manifest>]). The runtime of these manifests should be rolled into the runtime
of the parent manifest as that is how it will be run in CI.

This change also updates the runtimes files to incorporate this change.

Differential Revision: https://phabricator.services.mozilla.com/D55285

--HG--
extra : moz-landing-system : lando
2019-12-02 21:21:36 +00:00
..
README.md Bug 1583364 - Update testing/runtimes/writeruntimes script to write info at the manifest level, r=gbrown 2019-11-23 05:29:35 +00:00
manifest-runtimes-android.json Bug 1600314 - [runtimes] Don't store runtime information for included manifests, r=gbrown 2019-12-02 21:21:36 +00:00
manifest-runtimes-unix.json Bug 1600314 - [runtimes] Don't store runtime information for included manifests, r=gbrown 2019-12-02 21:21:36 +00:00
manifest-runtimes-windows.json Bug 1600314 - [runtimes] Don't store runtime information for included manifests, r=gbrown 2019-12-02 21:21:36 +00:00
moz.build Bug 1583364 - Generate 'manifest-runtimes.json' and update mochitest harness to use it, r=gbrown 2019-11-23 05:29:32 +00:00
writeruntimes Bug 1600314 - [runtimes] Don't store runtime information for included manifests, r=gbrown 2019-12-02 21:21:36 +00:00

README.md

Test Runtimes

These files contain runtimes for test manifests in the tree. They are of the form:

{ '<path to manifest>': <average runtime in seconds> }

They are being used to normalize chunk durations so all chunks take roughly the same length of time.

Generating a Test Runtime File

The writeruntimes script can be used to generate this file:

$ ./writeruntimes

It will take awhile. You can optionally specify platforms or suites on the command line, but these should only be used for debugging purposes (not for committing an update to the data). For more info, see:

$ ./writeruntimes -- --help