Bug 864085
On Fri, Apr 26, 2013 at 2:06 PM, Kartikaya Gupta <kgu...@mozilla.com> wrote: > On 13-04-26 11:37 , Phil Ringnalda wrote: >> >> Unfortunately, engineering is totally indifferent to >> things like having doubled the cycle time for Win debug browser-chrome >> since last November. >> > > Is there a bug filed for this? I just cranked some of the build.json files > through some scripts and got the average time (in seconds) for all the jobs > run on the mozilla-central_xp-debug_test-mochitest-browser-chrome builders, > and there is in fact a significant increase since November. This makes me > think that we need a "resource usage regression" alarm of some sort too. > > builds-2012-11-01.js: 4063 > builds-2012-11-15.js: 4785 > builds-2012-12-01.js: 5311 > builds-2012-12-15.js: 5563 > builds-2013-01-01.js: 6326 > builds-2013-01-15.js: 5706 > builds-2013-02-01.js: 5823 > builds-2013-02-15.js: 6103 > builds-2013-03-01.js: 5642 > builds-2013-03-15.js: 5187 > builds-2013-04-01.js: 5643 > builds-2013-04-15.js: 6207 > > kats > > _______________________________________________ > 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
