We've had tinderboxes setup for a while now (~3 months) that create
debug builds and then run the full suite of unit tests on them with leak
and bloat logging enabled. We currently have a CentOS and MacOSX box
running in this config, with 2 Windows machines waiting on increasing
logging capacity. These machines (qm-leak-centos5-01 and
qm-leak-macosx-01) are currently reporting to the MozillaTest tinderbox
tree:
http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTestThere was a great clamor in the Fall of 2007 to get these machines
setup, but no one seems to have looked at them since, or at least I
haven't received any feedback about them. I figure either:
a) no one has had time to look,
b) the data they are providing is no good, or
c) the need has gone away.
On the off-chance that it's option a), I went through a day's worth of
tinderbox logs from each platform about a week ago and parsed out the
relevant error message to make it more manageable for someone to glance
at. This more compact analysis is here:
http://wiki.mozilla.org/User:ChrisCooper:UnittestingLeakAnalysisIf someone with more knowledge about the unit tests can have a quick
look at the failures, it would be appreciated. I'd love to knock out any
spurious failures and have the data be more meaningful, and maybe even
have people start looking at the leak/bloat data from these boxes too.
cheers,
--
coop
_______________________________________________
dev-performance mailing list
dev-performance@...
https://lists.mozilla.org/listinfo/dev-performance