gecko-dev/testing/mozharness
Andrew Halberstadt 35b752c904 Bug 1403325 - Use a single --sandbox-read-whitelist argument in mochitest and reftest, r=Alex_Gaynor
The main bug this fixes is that on reftest, the objdir needs to be added to the
whitelist on Windows. However, this only happens when running on Linux for some
reason.

Changing the --work-path and --obj-path arguments to --sandbox-read-whitelist
was more of a drive-by cleanup than anything necessary.

MozReview-Commit-ID: Dq8ZLETMzeM

--HG--
extra : rebase_source : 3d2cdda125205e76f86235eb373074899fe0789a
2017-09-26 16:36:43 -04:00
..
configs Bug 1403325 - Use a single --sandbox-read-whitelist argument in mochitest and reftest, r=Alex_Gaynor 2017-09-26 16:36:43 -04:00
docs Bug 1359988 - Remove mozharness docs related to gaia; r=mshal 2017-04-26 13:55:10 -07:00
examples
external_tools Bug 1401501 - ensure windows10 resolution is 1280x1024. r=ahal 2017-09-22 14:20:33 -04:00
manifestparser Bug 1395956 - Update gecko.readthedocs links to the new firefox-source-docs.mozilla.org location. r=chutten 2017-09-02 22:11:02 +05:30
mozfile
mozharness Bug 1403565 - Improve test-verify behavior when reftest reference file is modified; r=jmaher 2017-09-27 13:15:35 -06:00
mozinfo
mozprocess Bug 1373294 - Fix E305 (two blank lines after method or class) in files enabled by flake8 linter, r=jmaher 2017-06-15 12:10:59 -04:00
scripts Bug 1396905 - Support reftests in test-verify; r=jmaher 2017-09-23 09:07:03 -06:00
test bug 1399523, now that we run l10n-merge in-build, drop it from mozharness, r=Callek 2017-09-15 16:25:18 +02:00
LICENSE
README.txt
mach_commands.py
requirements.txt Bug 1392700 - Use Mercurial 4.3 in mozharness tests; r=aki 2017-08-22 10:14:32 -07:00
setup.cfg
setup.py Bug 1378422 - Add python 2 only classifiers to python modules under /testing, r=ahal 2017-08-19 04:19:06 +05:30
tox.ini Bug 1392700 - Use Mercurial 4.3 in mozharness tests; r=aki 2017-08-22 10:14:32 -07:00
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! =)