gecko-dev/testing/mozharness
Nick Alexander 54af9eac53 Bug 1366644 - Pre: Work around mach/mozharness/mozprocess output issue. r=maliu
It's unfortunate, but somehow the

run-task > mozharness > mach build > mach gradle > Gradle

causes Gradle to hang with no output.  We avoid the bug by avoiding
the `max_build_output_timeout > 0` branch in mozharness.  (These tasks
are all in Task Cluster, so they'll be killed eventually and it's not
a huge issue to remove the output timeout.)

MozReview-Commit-ID: 9wiLWS7kRQ9

--HG--
extra : rebase_source : 8c1ec73945494d3307148b3e7d0cd44815bab40a
2017-10-13 13:46:58 -07:00
..
configs Bug 1366644 - Pre: Work around mach/mozharness/mozprocess output issue. r=maliu 2017-10-13 13:46:58 -07:00
docs Bug 1359988 - Remove mozharness docs related to gaia; r=mshal 2017-04-26 13:55:10 -07:00
examples
external_tools Bug 1297515 - Make a copy of third_party/python/virtualenv under testing/mozharness, r=jlund 2017-10-12 12:22:39 -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 1409260 - Remove mozharness tc-vcs support. r=dustin,gps 2017-10-17 15:09:40 +09: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 1399956 - Add headless mochitests to taskcluster. r=jmaher 2017-10-16 16:15:45 -07: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! =)