On Thursday, 9 August 2012 15:35:28 UTC+1, Justin Lebar wrote: > Is there a plan to mitigate the coalescing on m-i? It seems like that > is a big part of the problem.
Reducing the amount of coalescing permitted would just mean we end up with a backlog of pending tests on the repo tip - which would result in tree closures regardless. So other than bug 690672 making sheriffs' lives easier, we just need more machines in the test pool - since it's simply a case of demand exceeding capacity. The situation is made worse now that we're adding new platforms (OS X 10.7, B2G GB, B2G ICS, Android Armv6, soon OS X 10.8, Win8 desktop, Win8 metro) faster than we're EOLing them - and we're pushing more changes per day than ever before [1]. From what I understand, Apple's aggressive hardware cycle is also making it difficult to expand the test pool [2]. On a more positive note, at the end of this cycle we should be able to turn off Android XUL on trunk trees [3], which will at least help improve the wait on that platform :-) [1] http://oduinn.com/blog/2012/08/04/infrastructure-load-for-july-2012/ [2] https://bugzilla.mozilla.org/show_bug.cgi?id=772458#c3 [3] https://bugzilla.mozilla.org/show_bug.cgi?id=777037#c4 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
