зеркало из https://github.com/mozilla/gecko-dev.git
26e9db86f8
We've long handled chunks by defining the total number of chunks in our CI configuration, and then passing that value down into the test harnesses at task runtime (via the '--this-chunk' and '--total-chunks' parameters). The test harness then runs an algorithm to determine which tests should be run in "this" chunk. There are several problems with this approach, but by far the biggest is that we can't use test information in our scheduling algorithms. The information simply isn't available yet. This patch switches things around such that we determine which tests go in which tasks during the taskgraph generation. This means we have perfect information around which tasks are running which tests, and if e.g a ccov or machine learning algorithm deems a particular test important, we can make sure to *only* schedule the tasks that contain that test. I'm planning to enable this a couple suites at a time so we don't accidentally stop running tests. This specifically only enables this mode for 'mochitest-media', 'mochitest-browser-chrome' and 'mochitest-devtools-chrome'. I chose these suites because they are the ones that are already using the 'chunk_by_runtime' algorithm. Differential Revision: https://phabricator.services.mozilla.com/D52729 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| docs | ||
| manifestparser | ||
| mozcrash | ||
| mozdebug | ||
| mozdevice | ||
| mozfile | ||
| mozhttpd | ||
| mozinfo | ||
| mozinstall | ||
| mozleak | ||
| mozlog | ||
| moznetwork | ||
| mozpower | ||
| mozprocess | ||
| mozprofile | ||
| mozproxy | ||
| mozrunner | ||
| mozscreenshot | ||
| mozsystemmonitor | ||
| moztest | ||
| mozversion | ||
| rust | ||
| README.md | ||
| moz.build | ||
| packages.txt | ||
| setup_development.py | ||
| versioninfo.py | ||
README.md
Mozbase
Mozbase is a set of easy-to-use Python packages forming a supplemental standard library for Mozilla. It provides consistency and reduces redundancy in automation and other system-level software. All of Mozilla's test harnesses use mozbase to some degree, including Talos, mochitest, and reftest.
Learn more about mozbase at the project page.
Read detailed docs online, or build them locally by running "make html" in the docs directory.