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
(Adding the tooltool step for local setup) |
Haftandilian (talk | contribs) (Typo) |
||
| (7 intermediate revisions by 5 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 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 48: | 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 3 - Find the command in the log === | === Step 3 - Find the command in the log === | ||
| Line 65: | Line 66: | ||
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 5 - Append --installer-url and/or --test-url === | === Step 5 - Append --installer-url and/or one of --test-url and --test-packages-url === | ||
Append ''--installer-url'' and | Append ''--installer-url'' and one of ''--test-url'' or ''--test-packages-url''. You can find the right values on the log: | ||
<pre> | <pre> | ||
08:14:31 INFO - Found installer url http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-inbound-linux32_gecko/1400225075/en-US/b2g-32.0a1.en-US.linux-i686.tar.bz2. | 08:14:31 INFO - Found installer url http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-inbound-linux32_gecko/1400225075/en-US/b2g-32.0a1.en-US.linux-i686.tar.bz2. | ||
08:14:31 INFO - Found test url http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-inbound-linux32_gecko/1400225075/en-US/b2g-32.0a1.en-US.linux-i686.tests.zip. | 08:14:31 INFO - Found test url http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-inbound-linux32_gecko/1400225075/en-US/b2g-32.0a1.en-US.linux-i686.tests.zip. | ||
… | |||
17:51:04 INFO - Found a test packages url https://queue.taskcluster.net/v1/task/XHPBpieOSeO2e44zhkw64A/artifacts/public/build/test_packages.json. | |||
</pre> | </pre> | ||
| Line 75: | Line 78: | ||
== Build and other jobs == | == Build and other jobs == | ||
You don't have to use --installer-url or --test-url. | You don't have to use --installer-url, --test-url, or --test-packages-url. | ||
Right now I have not been able to run too many of these jobs on my local machine since it requires setting up mock_mozilla and each of these jobs can have their own set of environments. | Right now I have not been able to run too many of these jobs on my local machine since it requires setting up mock_mozilla and each of these jobs can have their own set of environments. | ||
| Line 166: | 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 == | ||