Revision as of 22:11, 8 December 2014

In the A-team we have recently been focusing on making mozharness easier to use by developers and give more flexibility in its use. Mozharness was originally started with Release Engineering and the A-team has been able to use it to contribute on the side of test jobs.

Some of the changes agreed to be tackled over the next couple of quarters are defined in Mozharness changes. We will migrate that page into here.

Understanding mozharness

If you want to understand more about mozharness read this page.

Getting help

If you run a script and it fails, attach one of the log files under "logs/". It will contain all the information needed to give you a hand.

Browsing the code

You can use dxr to browse Mozharness's code. You can also use mxr to search repositories that are involved with mozharness.

Filing bugs

If you find any issues running mozharness locally, please let us know by filing a bug. If you could attach logs/log_raw.log to the bug it will help us see what you're facing.

Setup

Using mozharness is very easy. Here's what it takes to run it:

hg clone http://hg.mozilla.org/build/mozharness
cd mozharness

Check the "examples" section for seeing how to run mozharness locally.

NOTE: For some test jobs you will need LDAP credentials. This might limit the ability of community members to try those type of jobs.

Prerequisites

You need to have:

Mercurial
virtualenv

For Windows users you can get all this by installing MozillaBuild.

Examples

The following are some examples of test jobs that you can run locally: - Run a Firefox desktop reftest

On Linux:

python scripts/desktop_unittest.py --cfg unittests/linux_unittest.py --reftest reftest \
--installer-url ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-35.0a1.en-US.linux-x86_64.tar.bz2 \
--test-url ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-35.0a1.en-US.linux-x86_64.tests.zip \
--cfg developer_config.py

On Windows:

python scripts/desktop_unittest.py --cfg unittests/win_unittest.py --reftest-suite reftest \
--installer-url ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-35.0a1.en-US.win32.zip \
--test-url ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/7/firefox-35.0a1.en-US.win32.tests.zip \
--cfg developer_config.py

- Run a Firefox for Android reftest:

python scripts/android_emulator_unittest.py --cfg android/androidarm.py --test-suite reftest-1 \
--installer-url ftp://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android/fennec-35.0a1.en-US.android-arm.apk \
--test-url ftp://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android//fennec-35.0a1.en-US.android-arm.tests.zip \
--cfg developer_config.py

- Run a Firefox OS emulator reftest job (NOTE: You will need LDAP credentials):

python scripts/b2g_emulator_unittest.py --cfg b2g/emulator_automation_config.py --test-suite reftest --this-chunk 1 --total-chunks 20 \
--installer-url http://pvtbuilds.pvt.build.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-emulator/20141001060621/emulator.tar.gz \
--test-url http://pvtbuilds.pvt.build.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-emulator/20141001060621/b2g-35.0a1.en-US.android-arm.tests.zip \
--cfg developer_config.py

If you want to learn a bit more about different ways we can run jobs running in tbpl.mozilla.org locally, follow this article: "How to run Mozharness as a developer".

Testing your mozharness changes

You can try your changes locally and then ask for review. In the future, we would like to allow for testing of changes on the try server: bug 791924

Where can I help?

In order to make mozharness easier for developers we have to make it a delightful and well integrated experience. If you want to help, you can find the list of bugs needed to accomplish listed by difficulty.