On Sun, Nov 17, 2013 at 2:17 AM, smaug <sm...@welho.com> wrote: > > the recent OOM cases have been really annoying. They have slowed down > development, even for those who > haven't been dealing with the actual issue(s). > > Could we handle this kind of cases differently. Perhaps clone the bad state > of m-i to > some other repository we're tracking using tbpl, backout stuff from m-i to > the state where we can > run it, re-open it and do the fixes in the clone. > And then, say in a week, merge the clone back to m-i. If the state is still > bad (no one has step up to fix the > issues), then keep m-i closed until the issues have been fixed.
Sounds complicated. It also assumes that we can backout stuff to fix the problem; we tried that to some extent with the first OOM closure -- it is the standard response to test failure, of course -- but it didn't work. More generally, I don't like the idea of making this kind of breakage normal. I'd prefer to see effort go towards preventing it than tolerating it. Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
