Confirmed users
586
edits
ReleaseEngineering/Mozharness/How to run tests as a developer: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Mozharness/How to run tests as a developer (view source)
Revision as of 14:09, 13 February 2018
, 13 February 2018→Step 3 - B) Create a buildprops.json: Note about extra properties needed in buildprops.json
(→...on a loaner machine: note to use test-packages-url) |
(→Step 3 - B) Create a buildprops.json: Note about extra properties needed in buildprops.json) |
||
| 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 == | ||