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
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Make some ad-hoc manual updates to `testing/marionette/client/setup.py`, `testing/marionette/harness/setup.py`, and `testing/firefox-ui/harness/setup.py`, which have hard-coded regexes that break after the reformat.
5. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Make some ad-hoc manual updates to `testing/marionette/client/setup.py`, `testing/marionette/harness/setup.py`, and `testing/firefox-ui/harness/setup.py`, which have hard-coded regexes that break after the reformat.
5. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
Changes:
- `web-platform-tests-wdspec` and `web-platform-tests-crashtests` are newly added to the file.
- `web-platform-tests` groupings are changed.
Differential Revision: https://phabricator.services.mozilla.com/D80921
Changes:
Update `writeruntimes` script so that each suite is in its own nested dictionary and add the ability to query `web-platform-tests-reftest`.
Differential Revision: https://phabricator.services.mozilla.com/D75229
CLOSED TREE
Backed out changeset 93efb53380c2 (bug 1637463)
Backed out changeset 5c8ccda5f1b1 (bug 1637463)
Backed out changeset a5fc1b604238 (bug 1637463)
Changes:
Update `writeruntimes` script so that each suite is in its own nested dictionary and add the ability to query `web-platform-tests-reftest`.
Differential Revision: https://phabricator.services.mozilla.com/D75229
Changes:
After some iterations, it turns out that normalization of the test paths returned by web-platform-tests is unnecessary for the time being.
- removed normalization of the test paths from `writeruntimes`.
- updated manifest-runtime JSON files for all three platforms.
Differential Revision: https://phabricator.services.mozilla.com/D74264
Modify `writeruntimes` script to support the querying and writing of web-platform-test related runtimes. These are already stored on ActiveData, so it is simply a matter of querying them.
Changes:
- obtain the full list of web-platform-tests runtimes using ActiveData's destination/output clause.
- normalize the paths by prefixing `testing/web-platform` in front of the returned test paths and limiting the paths to depth of 1.
Differential Revision: https://phabricator.services.mozilla.com/D67554
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
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
As a side-effect this will also update runtime data for all suites using
'--chunk-by-runtime'.
This change simultaneously:
1. Stores runtime data from all suites
2. Stores runtime data from all tests (no more percentile)
3. Stores distinct data for android, unix (osx/linux) and windows
4. Reduces the size of 'testing/runtimes' from 408k -> 168k
The chunks look more balanced from my unscientific glance (especially on Windows).
Differential Revision: https://phabricator.services.mozilla.com/D53702
--HG--
extra : moz-landing-system : lando
The script should just do the thing that we want. Providing options just
increases the chance of user error. I don't see any need to specify either of
these things.
Depends on D53699
Differential Revision: https://phabricator.services.mozilla.com/D53700
--HG--
extra : moz-landing-system : lando
The main motivation here was to gain access to the mach enviroment for the
future refactor.
Depends on D53698
Differential Revision: https://phabricator.services.mozilla.com/D53699
--HG--
rename : testing/runtimes/writeruntimes.py => testing/runtimes/writeruntimes
extra : moz-landing-system : lando
As a side-effect this will also update runtime data for all suites using
'--chunk-by-runtime'.
This change simultaneously:
1. Stores runtime data from all suites
2. Stores runtime data from all tests (no more percentile)
3. Stores distinct data for android, unix (osx/linux) and windows
4. Reduces the size of 'testing/runtimes' from 408k -> 168k
The chunks look more balanced from my unscientific glance (especially on Windows).
Differential Revision: https://phabricator.services.mozilla.com/D53702
--HG--
extra : moz-landing-system : lando
The script should just do the thing that we want. Providing options just
increases the chance of user error. I don't see any need to specify either of
these things.
Depends on D53699
Differential Revision: https://phabricator.services.mozilla.com/D53700
--HG--
extra : moz-landing-system : lando