Confirmed users
1,759
edits
ReleaseEngineering/TryServer: Difference between revisions
m
→Re-running tasks with custom parameters from Treeherder
(→How to push to try: Try job from review phase I will add a screen shot) Tags: Mobile edit Mobile web edit |
|||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 27: | Line 27: | ||
For every patch submitted for review in Phabricator, a new Try run is automatically created. This run is created for static analysis, linting and other tasks. | For every patch submitted for review in Phabricator, a new Try run is automatically created. This run is created for static analysis, linting and other tasks. | ||
As described below, attaching new jobs to the run is easy and doesn't require more actions from the developer. | As described below, attaching new jobs to the run is easy and doesn't require more actions from the developer. | ||
Just click on the ''Treeherder Jobs''. | |||
[[File:Screenshot 2019-10-07 ⚙ D48316 Bug 1585593 - Enable Fission for Raptor.png]] | |||
For more details, see: | |||
https://firefox-source-docs.mozilla.org/tools/try/index.html#attaching-new-jobs-from-a-review | |||
=== Scheduling jobs with Mach Try === | === Scheduling jobs with Mach Try === | ||
| Line 44: | Line 50: | ||
default=<selector> | default=<selector> | ||
See [https://firefox-source-docs.mozilla.org/tools/try/selectors/index.html this documentation] for more information on all the available selectors. | See [https://firefox-source-docs.mozilla.org/tools/try/selectors/index.html this documentation] for more information on all the available selectors, and [https://firefox-source-docs.mozilla.org/tools/try/presets.html this document] for a list of available presets (derived from [https://searchfox.org/mozilla-central/source/tools/tryselect/try_presets.yml try_presets.yml]). | ||
| Line 121: | Line 127: | ||
* TryServer purpose is to tell what will happen on Tinderbox, not to check every possible build option/configuration. | * TryServer purpose is to tell what will happen on Tinderbox, not to check every possible build option/configuration. | ||
** Any non-standard feature is implicitly unsupported. You may try them, but don't complain if they break. | ** Any non-standard feature is implicitly unsupported. You may try them, but don't complain if they break. | ||
== Re-running tasks with custom parameters from Treeherder == | |||
It is possible to run a task again, with certain types of changes to its run time environment and parameters. This feature is commonly used to enable debug logging, or run a test repeatedly to reproduce test failures. | |||
In treeherder, select the job you want to re-run (Note: it currently only works for [https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/actions/retrigger_mochitest.py#30-31 some jobs]). The details panel should open. Look for the 3 dots icon ("Other job details") and select "Custom actions...". | |||
[[File:Custom-action.png|thumb|Selecting "Custom Action..." in treeherder.]] | |||
The <tt>retrigger-custom</tt> action is the one selected in the drop-down menu. Modify the task parameters as desired and select "Trigger". | |||
[[File:Custom Taskcluster Job Actions.png|thumb|Treeherder modal to request an action associated to a task]] | |||
This will schedule the task with your specified parameters. The new task will be labeled as <tt>custom-<original_task_name></tt>. | |||
Some of the parameters that you can change are (see screenshot above): | |||
* Environment variables (e.g. <tt>MOZ_LOG</tt>) | |||
* Modify Python's logging level | |||
* Path of the test to execute | |||
* Gecko preferences (think of <tt>about:config</tt>) | |||
* Run a test repeatedly | |||
* Run until the test fails | |||
Common problems: | |||
* By default the entire task is re-run, running all the tests in the original task. If repeat/runUntilFailure is specified, it may take a long time to repeat all the tests, and the log file may be huge. Consider using the path: parameter to limit the run to the test(s) of interest. | |||
== Getting debug symbols == | == Getting debug symbols == | ||
NOTE: You might be able to accomplish this by re-running a build task from Treeherder by adding the env variable to the new task. | |||
By default native debug symbols are not uploaded for Try server builds because of their size. If you want to debug your builds locally you must add <tt>MOZ_CRASHREPORTER_UPLOAD_FULL_SYMBOLS=1</tt> to the in-tree mozconfigs. You can do this for all platforms by importing [http://hg.mozilla.org/users/tmielczarek_mozilla.com/mq/raw-file/b44faf6cd177/enable-full-symbols this patch] into your mq and pushing it along with your changes to Try. This will cause a ...crashreporter-symbols-full.zip package to be uploaded to the builds directory for each platform built. | By default native debug symbols are not uploaded for Try server builds because of their size. If you want to debug your builds locally you must add <tt>MOZ_CRASHREPORTER_UPLOAD_FULL_SYMBOLS=1</tt> to the in-tree mozconfigs. You can do this for all platforms by importing [http://hg.mozilla.org/users/tmielczarek_mozilla.com/mq/raw-file/b44faf6cd177/enable-full-symbols this patch] into your mq and pushing it along with your changes to Try. This will cause a ...crashreporter-symbols-full.zip package to be uploaded to the builds directory for each platform built. | ||