зеркало из https://github.com/mozilla/gecko-dev.git
9e9fc55acc
These regexes are used for things like determining which tasks to run given a "path" int |mach try|. Previously, we used patterns like: mochitest-chrome-(?:e10s)?(?:-1)?$ This would match both e10s and non-e10s versions of a task with either no chunks, or only selecting chunk 1. But we keep adding other configurations, e.g -gpu, -no-accel, -sw, etc. Each time we create a new possibility we need to remember to update these task regexes (or else lose test coverage when using paths with |mach try|). Instead of individually listing every possibility, let's use a pattern like this: mochitest-chrome($|.*(-1|[^0-9])$) This also selects tasks that are either chunk 1 or don't have any chunks. But it allows for arbitrary strings in-between. This regex doesn't need to be updated when we add configurations like -sw. Depends on D7119 Differential Revision: https://phabricator.services.mozilla.com/D7120 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| awsy | ||
| config | ||
| crashtest | ||
| firefox-ui | ||
| geckodriver | ||
| gtest | ||
| jsshell | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| profiles | ||
| raptor | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| tools | ||
| tps | ||
| web-platform | ||
| webdriver | ||
| xpcshell | ||
| README.txt | ||
| cppunittest.ini | ||
| mach_commands.py | ||
| moz.build | ||
| remotecppunittests.py | ||
| runcppunittests.py | ||
| testsuite-targets.mk | ||
README.txt
Common testing tools for mozilla codebase projects, test suite definitions for automated test runs, tests that don't fit anywhere else, and other fun stuff