Confirmed users
1,759
edits
ReleaseEngineering/TryServer: Difference between revisions
→Re-running tasks with custom parameters from Treeherder
(Add a note on the presets created by try_presets.yml) |
|||
| Line 129: | Line 129: | ||
== 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...". | 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...". | ||
| Line 148: | Line 150: | ||
* 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 == | ||