|
|
| Line 76: |
Line 76: |
|
| |
|
| === Retriggering Browsertime Visual Metrics Tasks === | | === Retriggering Browsertime Visual Metrics Tasks === |
| | | For details on retriggering/backfilling visual metrics tasks see [[/VisualMetrics/]]. |
| After running Browsertime 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:
| |
| | |
| * Select a browsertime test task (not a vismet task) that you want to retrigger.
| |
| * In the Treeherder pop-up menu, select the <tt>...</tt> and click on <tt>Custom Action</tt>.
| |
| * Pick the <tt>retrigger</tt> action if it wasn't already selected.
| |
| * Set <tt>downstream</tt> to <tt>true</tt>.
| |
| * Enter the number of times it should be retriggered in <tt>times</tt>.
| |
| * Retrigger!
| |
| | |
| See [https://bugzilla.mozilla.org/show_bug.cgi?id=1602893 bug 1602893] for more information on this issue.
| |
| | |
| 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 <tt>vismet</tt> job and it will trigger the test task.
| |
|
| |
|
| === Upgrading Browsertime In-Tree === | | === Upgrading Browsertime In-Tree === |