Bug 456274 comment 3: { From Serge Gautherie 2008-09-21 13:45:11 PDT TUnit: Could be (a little) harder as ("all") output does to their individual log files, but it would be worse doing it (as I check them locally), as it does/can have leaks ! reftest + crashtest: (I haven't run them yet, so I can't say, though I would think it couldn't hurt to monitor them too.) } Bug 456274 comment 4: { From Ted Mielczarek (:luser) 2008-09-22 03:45:21 PDT Probably worth filing separate bugs for implementing leak tracking in TUnit and reftest. }

Triaged to Future.

CC Clint, as we briefly spoke about it at "Mozilla Camp Europe 2008".

Iirc: { Waldo> sdwilsh: we'd need generic leak-log parsing code for that, too; easy to whip up from existing stuff in runtests.py, but not done sgautherie> I would think we need a python script to parse all the log files ... looks +/- trivial, with mochitest example, but I don't know enough python yet... ted> also, if someone rewrote the xpcshell unit test harness in python, i would not shed a tear }

Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.

Ping - is there any plan to work on this soon/ever?

Morphing to reftest since TUnit doesn't exist these days.