зеркало из https://github.com/mozilla/gecko-dev.git
66779f5fbc
The virtualenv is placed in the "work dir" by default. If we clobber the "work dir" at the beginning of the job, the parent directory of the virtualenv may not exist and virtualenv creation will fail because we set cwd to the work dir. Fix that by ensuring the work dir / cwd always exists when creating the virtualenv. MozReview-Commit-ID: FAZPP1Sm22k --HG-- extra : rebase_source : 126443cbcd5c83aeb47848bfc90ae28be9c9f596 |
||
|---|---|---|
| .. | ||
| 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! =)