202
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 00:28, 21 March 2018
, 21 March 2018Typo
(remove old standalone mozharness repo) |
Haftandilian (talk | contribs) (Typo) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 23: | Line 23: | ||
* If the job is... | * If the job is... | ||
** A build job: nothing to append | ** A build job: nothing to append | ||
** A test job: append --installer-url and --test-url | ** A test job: append --installer-url and one of --test-url or --test-packages-url | ||
** A talos job: append --installer-url | ** A talos job: append --installer-url | ||
| Line 49: | Line 49: | ||
* Issue a new user token with tooltool.download.public and tooltool.download.internal selected | * Issue a new user token with tooltool.download.public and tooltool.download.internal selected | ||
* The token will only be shown once | * The token will only be shown once | ||
* Place it in / | * Place it in ~/.mozilla/releng/relengapi.tok | ||
=== Step | === 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. | ||
| Line 169: | Line 169: | ||
In the previous section we mention to use --installer-url as well as --test-url, this is not necessary if you create a file called buildprops.json since the URLs are already specified inside of it. | In the previous section we mention to use --installer-url as well as --test-url, this is not necessary if you create a file called buildprops.json since the URLs are already specified inside of it. | ||
You can find the information you need by loading a tbpl log and looking for ''"08:14:31 INFO - Using buildbot properties"''. | You can find the information you need by loading a tbpl log and looking for ''"08:14:31 INFO - Using buildbot properties"''. | ||
Don't try to make sense of it. Just copy it without the datestamps (I know, it sucks). | Don't try to make sense of it. Just copy it without the datestamps (I know, it sucks). You will also need to add some dummy properties which you can find at https://searchfox.org/mozilla-central/source/taskcluster/docker/recipes/buildprops.json because the Python code that reads the file looks for these. | ||
== Step 4 - B) --no-read-buildbot-config == | == Step 4 - B) --no-read-buildbot-config == | ||