mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-27 04:05:32 +00:00
ed7bf22170
The system resource utilization during job execution is important: it gives us an idea of the efficiency (or lack thereof) of activities. As bug 1271035 showed us, there can be some really wonky things going on during job execution. To help us notice these things, this commit prints some overall resource utilization data with the special "TinderboxPrint" syntax so it appears in Treeherder. This should hopefully draw the attention of more eye balls and cause people to ask questions about what jobs are doing. This supplements the existing printing of total resource usage in the logs. Unfortunately nobody was really looking at that data because it wasn't exposed that well. This commit should change that. MozReview-Commit-ID: AXNRDS9lrOd --HG-- extra : rebase_source : c5e6b440092853649456d89a1f7dc370ca4ec29a |
||
---|---|---|
.. | ||
configs | ||
docs | ||
examples | ||
external_tools | ||
mozfile | ||
mozharness | ||
mozinfo | ||
mozprocess | ||
scripts | ||
test | ||
LICENSE | ||
mach_commands.py | ||
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! =)