When mochitests fail due to leaks, they should TinderboxPrint: something to indicate that they failed due to leaks. This makes it clear that a reason for the orange is leaks without having to view the log. This is particularly important when there are multiple failures happening at the same time (like right now), and nobody would notice that leaks have started until the test failure that's also causing orange is fixed.
We could very easily do this in runtests.py, as long as you don't mind that the leak output would wind up above the summary numbers, since those are generated by buildbot after the tests are run, so you'd see something like: LEAKED mochitest:10000/0/100
Sounds a lot better than nothing (although not perfect). (How hard would it be to say "mochitest: LEAKED"?)
This is definitely hurting us, bug 446044 for example.
Component: Testing → Mochitest
Product: Core → Testing
QA Contact: testing → mochitest
Version: Trunk → unspecified
Fixing this would help clear out "intermittent unittest weirdness".
(In reply to comment #3) > This is definitely hurting us, bug 446044 for example. I bet it would help bug 448125 too.
(In reply to comment #0) It looks like you filed this again as bug 468577 :-/ R.Fixed, by it. (Not duplicating, per dependent bugs and CC list here.)
Assignee: ted.mielczarek → nobody
Status: NEW → RESOLVED
Closed: 11 years ago
Depends on: 468577
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.