Confirm
3,990
edits
Changes
Add section about re-running tasks with custom parameters
* 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.
== Re-running tasks with custom parameters from Treeherder ==
Load a job you're interested to re-run (Note it currently only work for [https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/actions/retrigger_mochitest.py#30-31 some jobs]). The details panel should open up. Look for the 3 dots icon ("Other job details") and select "Custom actions...".
[[File:Custom Taskcluster Job Actions.png|thumb|Treeherder modal to request an action associated to a task]]
The <tt>retrigger-mochitest</tt> action (TODO: A better name is needed) is the one selected in the dropdown menu. You can now modify some parameters of the task and select "Trigger". This will schedule the task with your specified parameters. The 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 preference (think of <tt>about:config</tt>)
* Run a test repeatedly
* Run until the test fails
== 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.
