When DEV/QA is running at the code coverage results that are supplied by RE at http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/experimental/codecoverage/ which I am hosting at http://people.mozilla.com/~mnandigama/codecoverage_html/ we see variations in coverage between runs. In order to understand these variations, we are required to look at the mochitest log file to debug [ to see how many tests are actually run or not ] This is becoming a regular requirement. Can you kindly add the mochitest log as a separate file to the tar ball ... so that we don't need to trouble catlee on a daily basis ? Thanks Murali
Release Engineering bugs go in mozilla.org : Release Engineering, for future reference. (Build Config is for bugs about the build system.)
Component: Build Config → Release Engineering
Product: Firefox → mozilla.org
QA Contact: build.config → release
Version: unspecified → other
Is there any reason we can't just have this report to a Tinderbox waterfall instead?
It does, it reports to the Testing waterfall: http://tinderbox.mozilla.org/showbuilds.cgi?tree=Testing
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.