>> Is there a plan to mitigate the coalescing on m-i? It seems like that >> is a big part of the problem. > > it's simply a case of demand exceeding capacity.
Understood. But I think my question still stands: Is there a plan to address the fact that we do not have capacity to run all the tests we need to run? It sounds like [2] the answer is no, for at least the medium-term, because releng is busy deploying Mac 10.8 and Windows 8. I do not think we can afford to wait on these large projects before deploying more hardware. I'd like to see data, but it seems to me that we've hugely regressed tryserver turnaround times in the past few months. Unless we're able to add more machines to the pool, there is no end in sight. It seems that we need a concrete promise from releng / it to keep end-to-end tryserver times (push to final test finished) below X hours at the 90th percentile, and to coalesce fewer than Y% of pushes to m-i/m-c (measured during the busiest Z hours of each day). Then there's no need to guess about whether the pool is unacceptably backed up, or whether fixing the pile-up should be a priority. -Justin [2] https://bugzilla.mozilla.org/show_bug.cgi?id=772458#c3 On Tue, Aug 14, 2012 at 3:14 PM, Ed Morley <bmo.takethis...@edmorley.co.uk> wrote: > 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 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
