On 3/25/14, 3:14 PM, Andrew Halberstadt wrote:
With the completion of bug 981030 test harness options are now defined
in-tree.
This means any push without this patch [1] will fail. I already went
ahead and landed it on all release branches, but if you have an
integration or project branch, you may need to merge m-c in (or cherry
pick that patch) to get things working again. If you want to push to try
based on a rev that doesn't have it, you'll need to land it alongside
the other changes you are pushing. Sorry for the inconvenience!
Why did I do this? There are several benefits:
A) We can easily modify the command line to the harness without needing
to worry about affecting older branches.
B) It is now very easy to push custom command lines to try.
To push a custom command line to try, go to testing/config/mozharness,
open the file(s) corresponding to the platform you want to change, and
edit the '<suite>_options' key where suite is the name of the test
harness (e.g mochitest, reftest, etc..).
This is awesome and opens up many new possibilities. I want to
underscore that to readers.
Before, if we wanted to experiment with a new command line option for
the test harnesses, remove an old option, or just play around with
existing options, we typically had to hack up the test harnesses
themselves - a daunting task for the uninitiated! This change makes it
possible for people to experiment and do new and crazy things without
requiring anyone to get involved (previously these things likely
required a new project branch, modifying mozharness or buildbot configs,
etc and was very people intensive). Now, individuals have power. If you
can push to Try you can experiment! Want to add --shuffle to mochitests:
change some JSON-looking Python and push to Try. Want to run the
disabled long-running tests: remove an argument and push to Try. This is
a game changer. Self service for the win.
Andrew: I'm curious if you or anyone else has given any consideration
into making it dead simple to change the config so only a subset of
tests will be active. e.g. I'd like to save automation resources and
filter my browser chrome jobs to tests under toolkit/mozapps/extensions.
This is now possible but requires modifying N config files under
testing/config/mozharness. Could we get that down to 1 or added to Try
syntax somehow?
This is so awesome.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
