зеркало из https://github.com/mozilla/gecko-dev.git
da32e2ee18
From changeset de41dae85307ad65523a7dd2e9ae788490860bdc in the version-control-tools repository. Added without modifications. This adds automatic retry functionality to hopefully cut down on the number of intermittent failures related to connectivity problems. Self reviewing because the extension changes were already peer reviewed. MozReview-Commit-ID: 2vMpM2QHExL --HG-- extra : rebase_source : 82db28bb9751785801c319a4f9c49d24d61d446b |
||
---|---|---|
.. | ||
configs | ||
docs | ||
examples | ||
external_tools | ||
mozfile | ||
mozharness | ||
mozinfo | ||
mozprocess | ||
scripts | ||
test | ||
LICENSE | ||
README.txt | ||
mach_commands.py | ||
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! =)