> Is this what you're saying? > * 10.6 opt tests - per-checkin (no change) > * 10.6 debug tests - reduced > * 10.7 opt tests - reduced > * 10.7 debug tests - reduced > > * reduced --> m-c, m-a, m-b, m-r, esr17
Yes. Now that I think about this more, maybe we should go big or go home: change 10.6 opt tests to reduced as well, and see how it goes. We can always change it back. If it goes well, we can try to do the same thing with the Windows tests. We should get the sheriffs to sign off. On Thu, Apr 25, 2013 at 2:47 PM, Armen Zambrano Gasparnian <arme...@mozilla.com> wrote: > On 2013-04-25 2:39 PM, Justin Lebar wrote: >>>> >>>> We could come to the compromise of running them on m-c, m-a, m-b and >>>> m-r. Only this would help a lot since most of the load comes from m-i and >>>> try. We could make it a non-by-default platform on try. >> >> I wonder if we should do the same for debug 10.6 tests (and maybe builds). > > Is this what you're saying? > * 10.6 opt tests - per-checkin (no change) > * 10.6 debug tests - reduced > * 10.7 opt tests - reduced > * 10.7 debug tests - reduced > > * reduced --> m-c, m-a, m-b, m-r, esr17 > > >> >> The fact of the matter is that coalescing reduces our test coverage on >> m-i as it is; so long as we run these tests on central and we're OK >> with occasional bustage there, this seems pretty reasonable to me. > > Great! _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
