TestEngineering/Performance/Raptor/Browsertime/VisualMetrics: Difference between revisions
< TestEngineering | Performance | Raptor | Browsertime
Jump to navigation
Jump to search
(Created page with "= Retriggering Tasks = After running tests with visual metrics enabled on try you will notice that retriggering the tasks (along with the vismet tasks) is not straightforward....") |
(→Retriggering Tasks: Added old method of retriggering tests.) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
= Retriggering Tasks = | = Retriggering Tasks = | ||
After running tests with visual metrics enabled on try you will notice that retriggering the tasks (along with the vismet tasks) is not straightforward. To retrigger them correctly, you will have to do the following: | After running tests with visual metrics enabled on try you will notice that retriggering the tasks (along with the vismet tasks) is not straightforward. To retrigger them correctly, you will have to one of the following: | ||
* Select a browsertime test task (not a vismet task) that you want to retrigger. | |||
* In the Treeherder pop-up menu, select the ... and click on Custom Action. | |||
* Pick the retrigger action if it wasn't already selected. | |||
* Set downstream to true. | |||
* Enter the number of times it should be retriggered in times. | |||
* Retrigger! | |||
Or you can do the following: | |||
* In Treeherder, select the vismet task that you want to retrigger. | * In Treeherder, select the vismet task that you want to retrigger. | ||
| Line 7: | Line 16: | ||
* Under Dependencies click the browsertime task.<br>[[File:Parent page load task.png|thumb|none]] | * Under Dependencies click the browsertime task.<br>[[File:Parent page load task.png|thumb|none]] | ||
* Scroll up and click the Treeherder job link.<br>[[File:Link to Treeherder job.png|thumb|none]] | * Scroll up and click the Treeherder job link.<br>[[File:Link to Treeherder job.png|thumb|none]] | ||
* In the job details panel click the … and select Custom Action. | * In the job details panel click the … and select Custom Action.<br>[[File:Trigger custom action.png|thumb|none]] | ||
* Select the retrigger action if it wasn't already selected. | * Select the retrigger action if it wasn't already selected. | ||
* Set downstream to true. | * Set downstream to true. | ||
* Enter the number of times it should be retriggered in times.<br>[[File:Retriggering with downstream tasks.png|thumb|none]] | * Enter the number of times it should be retriggered in times.<br>[[File:Retriggering with downstream tasks.png|thumb|none]] | ||
* Retrigger! | * Retrigger! | ||
See {{bug|1602893}} for more information on this issue. | See {{bug|1602893}} for more information on this issue. | ||
Latest revision as of 15:41, 6 January 2021
Retriggering Tasks
After running tests with visual metrics enabled on try you will notice that retriggering the tasks (along with the vismet tasks) is not straightforward. To retrigger them correctly, you will have to one of the following:
- Select a browsertime test task (not a vismet task) that you want to retrigger.
- In the Treeherder pop-up menu, select the ... and click on Custom Action.
- Pick the retrigger action if it wasn't already selected.
- Set downstream to true.
- Enter the number of times it should be retriggered in times.
- Retrigger!
Or you can do the following:
- In Treeherder, select the vismet task that you want to retrigger.
- Click the Task link to inspect it in TaskCluster.
- Under Task Details click See More.
- Under Dependencies click the browsertime task.
- Scroll up and click the Treeherder job link.
- In the job details panel click the … and select Custom Action.
- Select the retrigger action if it wasn't already selected.
- Set downstream to true.
- Enter the number of times it should be retriggered in times.
- Retrigger!
See bug 1602893 for more information on this issue.
Backfilling Tasks
If you are back-filling jobs for finding a performance regression and an existing push does not have the target test, then when you are selecting the test to run, make sure you select the vismet job and it will trigger the test task.