ReleaseEngineering/TryServer - Revision history

Gbrown: /* Re-running tasks with custom parameters from Treeherder */

2020-03-05T22:21:54Z

Re-running tasks with custom parameters from Treeherder

← Older revision		Revision as of 22:21, 5 March 2020
Line 136:		Line 136:
	[[File:Custom-action.png\|thumb\|Selecting "Custom Action..." in treeherder.]]		[[File:Custom-action.png\|thumb\|Selecting "Custom Action..." in treeherder.]]

	The <tt>retrigger-~~mochitest~~</tt> action ~~(TODO: A better name is needed)~~ is the one selected in the drop-down menu. Modify the task parameters as desired and select "Trigger".		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]]

Gbrown: /* Re-running tasks with custom parameters from Treeherder */

2020-03-02T15:29:02Z

Re-running tasks with custom parameters from Treeherder

← Older revision		Revision as of 15:29, 2 March 2020
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 ==

Jonathan Watt: Add a note on the presets created by try_presets.yml

2020-02-21T14:31:58Z

Add a note on the presets created by try_presets.yml

← Older revision		Revision as of 14:31, 21 February 2020
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]).

Gbrown: /* Re-running tasks with custom parameters from Treeherder */

2020-02-12T15:24:00Z

Re-running tasks with custom parameters from Treeherder

← Older revision		Revision as of 15:24, 12 February 2020
Line 132:		Line 132:
	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...".

	[[File:Custom-action.png\|~~frame~~\|Selecting "Custom Action..." in treeherder.]]		[[File:Custom-action.png\|thumb\|Selecting "Custom Action..." in treeherder.]]

	The <tt>retrigger-mochitest</tt> action (TODO: A better name is needed) is the one selected in the drop-down menu. Modify the task parameters as desired and select "Trigger".		The <tt>retrigger-mochitest</tt> action (TODO: A better name is needed) is the one selected in the drop-down menu. Modify the task parameters as desired and select "Trigger".

Gbrown: /* Re-running tasks with custom parameters from Treeherder */

2020-02-12T15:23:23Z

Re-running tasks with custom parameters from Treeherder

← Older revision		Revision as of 15:23, 12 February 2020
Line 131:		Line 131:

	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...".

			[[File:Custom-action.png\|frame\|Selecting "Custom Action..." in treeherder.]]

			The <tt>retrigger-mochitest</tt> action (TODO: A better name is needed) 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]]

	~~The <tt>retrigger-mochitest</tt> action (TODO: A better name is needed) is the one selected in the drop-down menu. Modify the task parameters as desired and select "Trigger".~~ This will schedule the task with your specified parameters. The new task will be labeled as <tt>custom-<original_task_name></tt>.		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):

Gbrown: /* Re-running tasks with custom parameters from Treeherder */

2020-02-12T15:05:35Z

Re-running tasks with custom parameters from Treeherder

← Older revision		Revision as of 15:05, 12 February 2020
Line 130:		Line 130:
	== Re-running tasks with custom parameters from Treeherder ==		== 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...".		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 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]]

	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>.		The <tt>retrigger-mochitest</tt> action (TODO: A better name is needed) is the one selected in the drop-down menu. Modify the task parameters as desired and select "Trigger". 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 141:
	* Modify Python's logging level		* Modify Python's logging level
	* Path of the test to execute		* Path of the test to execute
	* Gecko ~~preference~~ (think of <tt>about:config</tt>)		* 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

Armenzg: Add section about re-running tasks with custom parameters

2020-02-04T20:39:17Z

Add section about re-running tasks with custom parameters

@@ Line 127: / Line 127: @@
 * 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.
 == Getting debug symbols ==
 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.

Sylvestre: Link to the in-tree doc

2019-11-27T07:54:29Z

Link to the in-tree doc

← Older revision		Revision as of 07:54, 27 November 2019
Line 31:		Line 31:

	[[File:Screenshot 2019-10-07 ⚙ D48316 Bug 1585593 - Enable Fission for Raptor.png]]		[[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 ===

Sylvestre: Add a screenshot

2019-10-07T13:17:38Z

Add a screenshot

← Older revision		Revision as of 13:17, 7 October 2019
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]]
	=== Scheduling jobs with Mach Try ===		=== Scheduling jobs with Mach Try ===

Sylvestre: /* How to push to try */Try job from review phase I will add a screen shot

2019-10-06T12:19:35Z

How to push to try: Try job from review phase I will add a screen shot

← Older revision		Revision as of 12:19, 6 October 2019
Line 23:		Line 23:
	== How to push to try ==		== How to push to try ==
	There are a few ways to schedule jobs on try.		There are a few ways to schedule jobs on try.

			=== Attach new jobs from the review ===

			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.

	=== Scheduling jobs with Mach Try ===		=== Scheduling jobs with Mach Try ===