83
edits
TestEngineering/Performance/Raptor/Browsertime: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Raptor/Browsertime (view source)
Revision as of 21:46, 14 January 2020
, 14 January 2020Added information on how to retrigger visual metric browsertime tasks.
(Added alternate chromedriver sync method) |
(Added information on how to retrigger visual metric browsertime tasks.) |
||
| Line 75: | Line 75: | ||
./mach try fuzzy --browsertime -q "'test-android-hw-g5-7-0-arm7-api-16/opt-raptor-tp6m-1-geckoview-e10s" | ./mach try fuzzy --browsertime -q "'test-android-hw-g5-7-0-arm7-api-16/opt-raptor-tp6m-1-geckoview-e10s" | ||
=== Retriggering Browsertime Visual Metrics Tasks === | |||
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. | |||
=== Upgrading Browsertime In-Tree === | === Upgrading Browsertime In-Tree === | ||