Confirmed users
1,759
edits
ReleaseEngineering/TryServer: Difference between revisions
m
→Re-running tasks with custom parameters from Treeherder
(Add section about re-running tasks with custom parameters) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 50: | 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 130: | Line 130: | ||
== Re-running tasks with custom parameters from Treeherder == | == 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]] | [[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): | Some of the parameters that you can change are (see screenshot above): | ||
| Line 141: | Line 147: | ||
* Modify Python's logging level | * Modify Python's logging level | ||
* Path of the test to execute | * Path of the test to execute | ||
* Gecko | * Gecko preferences (think of <tt>about:config</tt>) | ||
* Run a test repeatedly | * Run a test repeatedly | ||
* Run until the test fails | * 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 == | ||