зеркало из https://github.com/mozilla/gecko-dev.git
278fa528e2
There are two big parts in the MSVC toolchain we use: - the Windows 10 SDK - Visual C++ For the former, both the 15.8.4 and 15.9.6 toolchains are using the same version of the Win10 SDK. For the latter, we're not using the compiler itself anymore, so the only substantial difference is in the headers and libraries included with Visual C++, as well as the redist libraries for the CRT. Both versions are supposed to be compatible to the same set of OS versions, fitting our system requirements. This makes us use the same version of MSVC on all our Windows builds (arm64 builds were already on 15.9.6). Differential Revision: https://phabricator.services.mozilla.com/D123720 |
||
|---|---|---|
| .. | ||
| configs | ||
| docs | ||
| examples | ||
| external_tools | ||
| mozharness | ||
| scripts | ||
| test | ||
| LICENSE | ||
| README.txt | ||
| mach_commands.py | ||
| moz.build | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
| unit.sh | ||
README.txt
# Mozharness ## Docs * https://developer.mozilla.org/en-US/docs/Mozharness_FAQ * https://wiki.mozilla.org/ReleaseEngineering/Mozharness * http://moz-releng-mozharness.readthedocs.org/en/latest/mozharness.mozilla.html * http://moz-releng-docs.readthedocs.org/en/latest/software.html#mozharness ## Submitting changes Like any Gecko change, please create a patch or submit to Mozreview and open a Bugzilla ticket under the Mozharness component: https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness This bug will get triaged by Release Engineering ## Run unit tests To run the unit tests of mozharness the `tox` package needs to be installed: ``` pip install tox ``` There are various ways to run the unit tests. Just make sure you are within the `$gecko_repo/testing/mozharness` directory before running one of the commands below: ``` tox # run all unit tests tox -- -x # run all unit tests but stop after first failure tox -- test/test_base_log.py # only run the base log unit test ``` Happy contributing! =)