Bug 1549375 - Update try syntax for running damp tests in devtools documentation r=Honza
authorJulian Descottes <jdescottes@mozilla.com>
Mon, 13 May 2019 07:28:16 +0000
changeset 532411 b7145dad7ce17f1f8f72c8974b7472ffd1c84e17
parent 532410 194ec02ee76d472699c9458a1915df5430c82135
child 532412 8990b9990220bf229abe7c5f5ec6934802559af2
push id11268
push usercsabou@mozilla.com
push dateTue, 14 May 2019 15:24:22 +0000
treeherdermozilla-beta@5fb7fcd568d6 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersHonza
bugs1549375
milestone68.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1549375 - Update try syntax for running damp tests in devtools documentation r=Honza Differential Revision: https://phabricator.services.mozilla.com/D30350
devtools/docs/contributing/performance.md
devtools/docs/tests/performance-tests.md
devtools/docs/tests/tips.md
--- a/devtools/docs/contributing/performance.md
+++ b/devtools/docs/contributing/performance.md
@@ -131,17 +131,17 @@ It highlights that:
 ### Run performance tests
 
 See if any subtest reports a improvement. Ensure that the improvement makes any sense.
 For example, if the test is 50% faster, maybe you broke the performance test.
 This might happen if the test no longer waits for all the operations to finish executing before completing.
 
 To push your current patch to try, execute:
 ```
-./mach try -b o -p linux64 -u none -t damp-e10s --rebuild-talos 5 --artifact
+./mach try -b o -p linux64 -u none -t damp --rebuild-talos 5 --artifact
 ```
 It will print in your Terminal a link to perfherder like this one:
 [https://treeherder.mozilla.org/perf.html#/comparechooser?newProject=try&newRevision=9bef6cb13c43bbce21d40ffaea595e082a4c28db](https://treeherder.mozilla.org/perf.html#/comparechooser?newProject=try&newRevision=9bef6cb13c43bbce21d40ffaea595e082a4c28db)
 Running performance tests takes time, so you should open it 30 minutes up to 2 hours later to see your results.
 See [Performance tests (DAMP)](../tests/performance-tests.md) for more information about PerfHerder/try.
 
 Let's look at how to interpret an actual real-life [set of perfherder results](https://treeherder.mozilla.org/perf.html#/comparesubtest?originalProject=mozilla-central&newProject=try&newRevision=9bef6cb13c43bbce21d40ffaea595e082a4c28db&originalSignature=edaec66500db21d37602c99daa61ac983f21a6ac&newSignature=edaec66500db21d37602c99daa61ac983f21a6ac&showOnlyImportant=1&framework=1&selectedTimeRange=172800):
 
--- a/devtools/docs/tests/performance-tests.md
+++ b/devtools/docs/tests/performance-tests.md
@@ -12,21 +12,21 @@ This will run all DAMP tests, you can fi
 ```bash
 ./mach talos-test --activeTests damp --subtests console
 ```
 This command will run all tests which contains "console" in their name.
 
 ## How to run it on try?
 
 ```bash
-./mach try -b o -p linux64 -u none -t damp-e10s --rebuild-talos 6
+./mach try -b o -p linux64 -u none -t damp --rebuild-talos 6
 ```
 * Linux appears to build and run quickly, and offers quite stable results over the other OSes.
 The vast majority of performance issues for DevTools are OS agnostic, so it doesn't really matter which one you run them on.
-* "damp-e10s" is the talos bucket in which we run DAMP.
+* "damp" is the talos bucket in which we run DAMP.
 * And 6 is the number of times we run DAMP tests. That's to do averages between all the 6 runs and helps filtering out the noise.
 
 ## What does it do?
 
 DAMP measures three important operations:
 * Open a toolbox
 * Reload the web page
 * Close the toolbox
--- a/devtools/docs/tests/tips.md
+++ b/devtools/docs/tests/tips.md
@@ -13,10 +13,10 @@ export MOZ_QUIET=1
 
 You can also send `MOZ_QUIET` when you push to try&hellip; it makes the logs easier to read and makes the tests run faster because there is so much less logging.
 
 Example try syntax containing `MOZ_QUIET`:
 
 ```
 ./mach try -b do -p linux,linux64,macosx64,win32,win64 \
   -u xpcshell,mochitest-bc,mochitest-e10s-bc,mochitest-dt,mochitest-chrome \
-  -t damp-e10s --setenv MOZ_QUIET=1
+  -t damp --setenv MOZ_QUIET=1
 ```