ReleaseEngineering/Mozharness/How to run tests as a developer: Difference between revisions

Adding the tooltool step for local setup
(Adding the tooltool step for local setup)
Line 1: Line 1:
'''NOTE: If running a job does not easily run locally for you; don't hesitate to just stop (no need to try to fix it), [https://wiki.mozilla.org/ReleaseEngineering/How_To/Request_a_slave ask for a loaner so you can make progress] and file a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness here] for us to debug (please attach logs/log_info.log).'''
'''NOTE: You can now use your LDAP credentials to authenticate and download the files that are behind Http authentication (e.g. pvtbuilds).'''
'''NOTE: You can now use your LDAP credentials to authenticate and download the files that are behind Http authentication (e.g. pvtbuilds).'''


Line 39: Line 41:
  hg clone http://hg.mozilla.org/build/mozharness scripts
  hg clone http://hg.mozilla.org/build/mozharness scripts


=== Step 2 - Find the command in the log ===
=== 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.
 
Steps:
* Go [https://api.pub.build.mozilla.org/tokenauth here]
* Issue a new user token with tooltool.download.public and tooltool.download.internal selected
* The token will only be shown once
* Place it in /builds/relengapi.tok
 
=== Step 3 - 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.


NOTE: Don't forget to prepend ''python'' before the command.
NOTE: Don't forget to prepend ''python'' before the command.


=== Step 3 - Append --cfg developer_config.py ===
=== Step 4 - Append --cfg developer_config.py ===


{{warning|If you have a loaned machine from Release Engineering, do not use this config.<br/>This config is meant to be used only when you're running mozharness on your local machine.<br/>(<small>[[How_to_run_tests_as_a_developer#...on_a_loaner_machine|More Information]]</small>)}}
{{warning|If you have a loaned machine from Release Engineering, do not use this config.<br/>This config is meant to be used only when you're running mozharness on your local machine.<br/>(<small>[[How_to_run_tests_as_a_developer#...on_a_loaner_machine|More Information]]</small>)}}
Line 54: Line 65:
If you're trying to reproduce a unit test suite or a talos suite follow this last step. Otherwise, go to the "Build and other jobs" section.
If you're trying to reproduce a unit test suite or a talos suite follow this last step. Otherwise, go to the "Build and other jobs" section.


=== Step 4 - Append --installer-url and/or --test-url ===
=== Step 5 - Append --installer-url and/or --test-url ===
Append ''--installer-url'' and/or ''--test-url''. You can find the right values on the log:
Append ''--installer-url'' and/or ''--test-url''. You can find the right values on the log:
<pre>
<pre>
Confirmed users
3,990

edits