83
edits
TestEngineering/Performance/Raptor/Browsertime: Difference between revisions
TestEngineering/Performance/Raptor/Browsertime (view source)
Revision as of 16:21, 14 January 2021
, 14 January 2021→Retriggering Browsertime Visual Metrics Tasks: Update retriggering information
(→Finding the Geckodriver Being Used: Add information about geckodriver builds) |
(→Retriggering Browsertime Visual Metrics Tasks: Update retriggering information) |
||
| Line 90: | Line 90: | ||
=== Retriggering Browsertime Visual Metrics Tasks === | === Retriggering Browsertime Visual Metrics Tasks === | ||
For details on | |||
You can retrigger Browsertime tasks just like you retrigger any other tasks from Treeherder (using the retrigger buttons, add-new-jobs, retrigger-multiple, etc.). | |||
When you retrigger the Browsertime test task, it will trigger a new vismet task as well. If you retrigger a Browsertime vismet task, then it will cause the test task to be retriggered and a new vismet task will be produced from there. This means that both of these tasks are treated as "one" task when it comes to retriggering them. | |||
There is only one path that still doesn't work for retriggering Browsertime tests and that's happens when you use `--rebuild X` in a try push submission. | |||
For details on how we previously retriggered visual metrics tasks see [[/VisualMetrics/]] (this will stay here for a few months just in case). | |||
=== Gecko Profiling with Browsertime === | === Gecko Profiling with Browsertime === | ||