зеркало из https://github.com/mozilla/gecko-dev.git
f1fecc26b0
ensuring moz.build files have BUG_COMPONENTS for all files in the testing/ subdirectory is a win. There are a lot of older files and some files used in many harnesses. If the files are primarily used for mochitest, they are associated with the testing::mochitest component, otherwise I chose the testing::general component. There is an exception web-platform-tests, these have many test files that need to be matched to proper components. MozReview-Commit-ID: IIv9W2kEqeN |
||
|---|---|---|
| .. | ||
| README.md | ||
| mochitest-browser-chrome-e10s.runtimes.json | ||
| 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