hg push -f try.
try: -b o -p linux64 -u allcreates only an "opt" build on 64-bit Linux, and runs all of the tests on that build.
-bBuild type. Use
ofor an opt build (most common),
dfor a debug build, or
-pPlatform. There are five platforms. Each also has a
-shippablevariant, which is a complication you probably don't need to think about.
macosx64Mac OS (if you don't need a debug build, specify
allfor all platforms
-uUnit test suites.
try_task_config.jsonand containing a list of the tasks to run is included in one of the pushed revisions.
tasksis a list of tasks to run. In this example it's all of the 64-bit Linux tests. A 64-bit Linux build will also run, because it is required by the tasks specified.
try_task_config.jsonfile (or you want to add to an existing run), you can one or more tasks using Treeherder. Once the decision (D) task has completed, click the drop-down arrow to the right of it, and choose "Add new jobs".
./mach try emptyto push to the mozilla-central Try repository. You'll need to know the revision number of your push, which will be in the message printed to the console.
.gecko_rev.ymlto point to any revision on the mozilla-* trees to test your comm-central patch against them.
comm-esr##, the steps are the same as when doing a Try run for
comm-central. (For example, you do not need to change anything in your
hgrcfile.) The try server is smart enough to automatically detect which one to build and test. This works because of the
.gecko_rev.ymlfile. Note that some things might not work the same way as on
--artifactoption only works on