mochitests-4 generates very large (~25MB) log files, especially on OSX 10.6 debug builds This much data can take a while to process, so if there is any way to reduce the output, it would help out the infrastructure a lot. e.g. http://tinderbox.mozilla.org/Firefox/1280442576.1280451599.28060.gz
There's really not. Mochitest 4 doesn't do any different logging than mochitest 1, 2, 3, and 5. It's just that there happen to be tests in Mochitest 4 that write more messages to the log than others. The other problem here is that in order to remove "log messages" means we are removing checks, which essentially means that we would be changing test behavior. Every mochitest log message is the result of a test asserting that some behavior/variable is some value, so if we remove those we are effectively pulling the teeth out of our tests in a bid to save logging space, which seems like a backwards way of solving the problem. I'd rather not do that. Why don't we solve the real problem? What is the issue that the 25Mb log file causes? Can that be solved in some way? Or is that intractable?
Large log files were one of the factors contributing to the meltdown of Tinderbox as well as our buildbot masters. We seem to be in a better state load-wise currently, so this isn't as urgent.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.