Re: Test harness options now defined in-tree -- please pull m-c before pushing to try!

2014-03-26 Thread Andrew Halberstadt
On 26/03/14 01:45 PM, Nathan Froyd wrote: - Original Message - Releng (and I tend to agree with them) is very opposed to having one config affect multiple platforms (or at least multiple buildapps). Over time it tends to lead to messy and hard to follow configs. It also makes it harder i

Re: Test harness options now defined in-tree -- please pull m-c before pushing to try!

2014-03-26 Thread Nathan Froyd
- Original Message - > Releng (and I tend to agree with them) is very opposed to having one > config affect multiple platforms (or at least multiple buildapps). Over > time it tends to lead to messy and hard to follow configs. It also makes > it harder in the case that you *do* only want to

Re: Test harness options now defined in-tree -- please pull m-c before pushing to try!

2014-03-26 Thread Armen Zambrano G.
On 14-03-26 09:11 AM, Andrew Halberstadt wrote: > On 26/03/14 09:06 AM, Andrew Halberstadt wrote: >> On 26/03/14 12:19 AM, Gregory Szorc wrote: >>> 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

Re: Test harness options now defined in-tree -- please pull m-c before pushing to try!

2014-03-26 Thread Andrew Halberstadt
On 26/03/14 09:06 AM, Andrew Halberstadt wrote: On 26/03/14 12:19 AM, Gregory Szorc wrote: 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 an

Re: Test harness options now defined in-tree -- please pull m-c before pushing to try!

2014-03-26 Thread Andrew Halberstadt
On 26/03/14 12:19 AM, Gregory Szorc wrote: 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 to

Re: Test harness options now defined in-tree -- please pull m-c before pushing to try!

2014-03-25 Thread Gregory Szorc
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 m

Test harness options now defined in-tree -- please pull m-c before pushing to try!

2014-03-25 Thread Andrew Halberstadt
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