Confirmed users
328
edits
ReleaseEngineering/Mozharness/How to run tests as a developer: Difference between revisions
ReleaseEngineering/Mozharness/How to run tests as a developer (view source)
Revision as of 16:36, 26 October 2015
, 26 October 2015remove old standalone mozharness repo
Chmanchester (talk | contribs) (Update wording around --test-url and --test-packages-url to be more clear about what is required) |
(remove old standalone mozharness repo) |
||
| Line 37: | Line 37: | ||
== Common steps == | == Common steps == | ||
=== Step 1 - | === Step 1 - Check out mozharness === | ||
mozharness is now in the Gecko repository, under the testing/ directory. So if you do not already have a checkout, | |||
* hg clone https://hg.mozilla.org/mozilla-central/ | |||
=== Step 2 - Create a tooltool token (fetches artifacts for you) === | === Step 2 - Create a tooltool token (fetches artifacts for you) === | ||
With the new tooltool, you need to create a token to run mozharness on your development machine. | With the new tooltool, you need to create a token to run mozharness on your development machine. Note that this is not necessary for all mozharness scripts -- for example, the hazard builds do not require this as they only download public files via tooltool. | ||
Steps: | Steps: | ||
| Line 50: | Line 51: | ||
* Place it in /builds/relengapi.tok | * Place it in /builds/relengapi.tok | ||
=== Step | === Step 2 - Find the command in the log === | ||
In the job in treeherder you can search for '''"Run as scripts/scripts"''' and you should see how exactly the command was run in production and you can add the options mentioned above. | In the job in treeherder you can search for '''"Run as scripts/scripts"''' and you should see how exactly the command was run in production and you can add the options mentioned above. | ||