Having the control server shutdown the browser via the browser pid is a better (and cross-browser) solution.
MozReview-Commit-ID: 19Gwg5TwIIy
--HG--
extra : rebase_source : d1321889d784e526d2f5ec8a593000d97b7f0927
Some minor changes to allow running subtests in Raptor. With this patch (and the other commit in this series) you can run raptor tests that have mutliple subtests. For example, you can specify a raptor test INI and every test inside that INI will be run and ultimately reported as subtests. This will allow, for example, the raptor tp6 test to have multiple testpages. Also just one of the subtests itself can be specified to be run instead of the entire INI.
MozReview-Commit-ID: Fto7wNOzRft
--HG--
extra : rebase_source : 37d02fb43354fa0a799c7af9ea41c16670f2244c
This gets raptor to use the newly created "perf" profile that talos
also uses. There is a single pref that raptor sets that we can't set
in talos. To that end, this also creates a "raptor" specific profile.
This means to set a pref in talos and raptor, edit:
testing/profiles/perf/user.js
To set a pref in raptor only, edit:
testing/profiles/raptor/user.js
The performance of extensions can now be tested by dropping the
extension into:
testing/profiles/perf/extensions
MozReview-Commit-ID: LEJeytmmiFF
--HG--
extra : rebase_source : 0d2a6b18868f8cc6ff198ef868ad0324b57b1dc2
