mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-09 03:15:11 +00:00
eb87ca62cb
This greens up the openh264 build tasks and gets them running with python 3. I had a look at modernizing gittool.py, but that seemed complicated and unnecessary for our needs: we just need to checkout the git repo. There's some discussion about the Windows CFLAGS. I had a look and tried various approaches, but this was really the only way that worked for me (thanks jcristau!). Certainly I'm open to other suggestions...or we can revisit later. This change does not affect the signing format, which still requires work for OSX. Differential Revision: https://phabricator.services.mozilla.com/D149578 |
||
|---|---|---|
| .. | ||
| configs | ||
| docs | ||
| examples | ||
| external_tools | ||
| mozharness | ||
| 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! =)