зеркало из https://github.com/mozilla/gecko-dev.git
2782e27bed
Update runtimes data manually for new antitracking manifest. This data is normally updated by the writeruntimes script, but currently that is not working (it relies on ActiveData). I manually updated with approximate durations. Without an update to the runtime data, task scheduling is not aware that the new manifest is long-running, and schedules it alongside many other manifests, which continues to produce unbalanced test chunk run times; with the update, chunks are much more balanced. Differential Revision: https://phabricator.services.mozilla.com/D116639 |
||
|---|---|---|
| .. | ||
| README.md | ||
| manifest-runtimes-android.json | ||
| manifest-runtimes-unix.json | ||
| manifest-runtimes-windows.json | ||
| moz.build | ||
| writeruntimes | ||
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