canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,627
edits
ReleaseEngineering/TryChooser: Difference between revisions
Add information about tagging of tests.
m (mxr -> dxr) |
(Add information about tagging of tests.) |
||
| Line 1: | Line 1: | ||
TryChooser lets you select specific jobs you want to run on [https://wiki.mozilla.org/Build:TryServer tryserver]. You use TryChooser by putting a <tt>try:</tt> block at the end of the topmost commit message when you push to try. | [https://mozilla-releng.net/trychooser/ TryChooser] lets you select specific jobs you want to run on [https://wiki.mozilla.org/Build:TryServer tryserver]. You use TryChooser by putting a <tt>try:</tt> block at the end of the topmost commit message when you push to try. | ||
==Syntax Builder== | ==Syntax Builder== | ||
To simplify using the TryChooser, you can use the [ | '''To simplify using the TryChooser, you can use the [https://mozilla-releng.net/trychooser/ TryChooser Syntax Builder] website''' | ||
or the [http://hg.mozilla.org/users/pbiggar_mozilla.com/trychooser/file/tip mercurial extension] (which also functions as a command-line application, but is not maintained by RelEng). | or the [http://hg.mozilla.org/users/pbiggar_mozilla.com/trychooser/file/tip mercurial extension] (which also functions as a command-line application, but is not maintained by RelEng). | ||
| Line 110: | Line 110: | ||
**Look for your directory in [http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/ the builds FTP server] and see what has been uploaded. (You can also find here the email-changeset string that you'll need if you end up pinging releng.) | **Look for your directory in [http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/ the builds FTP server] and see what has been uploaded. (You can also find here the email-changeset string that you'll need if you end up pinging releng.) | ||
* Check [http://build.mozilla.org/buildapi/running/ Running] and [http://build.mozilla.org/buildapi/pending/ Pending] to view your build's status, since these are where Treeherder gets the job data from, so are closer to the source of truth. | * Check [http://build.mozilla.org/buildapi/running/ Running] and [http://build.mozilla.org/buildapi/pending/ Pending] to view your build's status, since these are where Treeherder gets the job data from, so are closer to the source of truth. | ||
===What if I want to run a sub-set of tests for a job?=== | |||
Tests can be tagged via the *.ini files, e.g. | |||
<pre> | |||
[default] | |||
tags = search | |||
</pre> | |||
or | |||
<pre> | |||
[default] | |||
[browser_426329.js] | |||
tags = search | |||
</pre> | |||
You can then run just the required tag by appending `--tag search` onto your try command, e.g. | |||
<pre> | |||
./mach try -b d -p linux64 -u mochitest-e10s-bc -t none --artifact --tag search | |||
</pre> | |||
==Parsing details== | ==Parsing details== | ||
| Line 127: | Line 150: | ||
=== Jobs not scheduled at all? === | === Jobs not scheduled at all? === | ||
Recreate the comment of their change with | Recreate the comment of their change with https://mozilla-releng.net/trychooser/ and compare it to make sure is correct. | ||
Then do a sendchange and tail the scheduler master: | Then do a sendchange and tail the scheduler master: | ||