mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-22 09:45:41 +00:00
26861a3269
Historically when invoking mach from mozharness on windows we have started it by way of bash. However, we haven't been doing that for `mach build check`. This hadn't caused noticeable issues in the past, but now that we are running rusttest builds, which wind up compiling extra Rust code in that step, intermittent failures are showing up because of this. The root cause is likely a bug in msys' translation of environment variables, but msys is unsupported and we're already using this workaround for the rest of the build. Differential Revision: https://phabricator.services.mozilla.com/D7816 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
configs | ||
docs | ||
examples | ||
external_tools | ||
manifestparser | ||
mozfile | ||
mozharness | ||
mozinfo | ||
mozprocess | ||
scripts | ||
test | ||
LICENSE | ||
mach_commands.py | ||
moz.build | ||
README.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
tox.ini | ||
unit.sh |
# 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! =)