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
- implement ekyle's tip for better grouping of run types
- combine build and run types and eliminate duplicates when building the platform name
- report '1proc' instead of 'e10s' so platform names look more similar to treeherder
The universal_newlines change is a ride-along, for improved py3 compat.
Differential Revision: https://phabricator.services.mozilla.com/D76211
The definition for reftest/crashtest variants of web-platform-tests in web-platform.yml has a trailing `s` which is technically incorrect.
This causes problems when querying ActiveData for the runtimes for these subsuites since the suite name recorded in ActiveData has the trailing s.
Changes:
- remove the trailing `s` from the definitions
Differential Revision: https://phabricator.services.mozilla.com/D68069
--HG--
extra : moz-landing-system : lando
A quick and basic implementation of 'mach test-info report-diff' to provide a
high level comparison of two reports generated by 'mach test-info report'.
Mostly this is trying to give an impression of how many and which tests
have been added and deleted during the time period between the reports.
There is more information in the reports; a more thorough comparison is
possible, but seems lower-value: To be considered in a future bug.
Differential Revision: https://phabricator.services.mozilla.com/D65202
--HG--
extra : moz-landing-system : lando
Minor changes to test-info report's interaction with ActiveData:
- with improved reftest data in ActiveData, several path modifications can
be removed;
- adjust some crashtest query data ranges to more efficiently handle the
new data;
- add a missing path modification for xpcshell, to handle test names that
include manifests.
Differential Revision: https://phabricator.services.mozilla.com/D60551
--HG--
extra : moz-landing-system : lando
When an ActiveData query returns HTTP 200 but no data, treat that as a permanent condition:
Do not retry. I expect that will be the case for some test-info queries for reftests
until reftest test names are normalized.
Differential Revision: https://phabricator.services.mozilla.com/D57892
--HG--
extra : moz-landing-system : lando
Currently 'mach test-info report --show-activedata' makes over a dozen requests to
ActiveData, one at a time. Most of the elapsed time for generating the report is
waiting for a response from ActiveData. A significant run-time savings is achieved
using threads to submit multiple requests concurrently.
Differential Revision: https://phabricator.services.mozilla.com/D57041
--HG--
extra : moz-landing-system : lando
Adjust ActiveData queries so that no query matches more than the ActiveData maximum
of 10000 records (crashtest excepted, until bug 1596567 is fixed). This provides a
dramatic improvement in the quality of run counts and run times reported for wpt and
reftests. Also adjusts some of the update mechanisms to handle duplicate paths better.
Also adds more (verbose) logging of match counts, report run times, etc in anticipation
of further refinements.
Differential Revision: https://phabricator.services.mozilla.com/D56616
--HG--
extra : moz-landing-system : lando
Move almost all test-info code out of mach_commands.py and into its own file
and consolidate logging and imports; no functional changes.
Differential Revision: https://phabricator.services.mozilla.com/D56064
--HG--
extra : moz-landing-system : lando