Hi folks- After a long delay I've finally integrated my logspam tools <https://github.com/EricRahm/log-spam-hell> into mach <https://bugzilla.mozilla.org/show_bug.cgi?id=1306503>. For reference, see some past discussions on the War on Warnings <https://lists.mozilla.org/pipermail/dev-platform/2015-June/010221.html>.
*What is logspam <https://bugzilla.mozilla.org/show_bug.cgi?id=765224> you ask?* It's the warning spew we see when running debug builds, particularly during testing. Sometimes these warnings are useful and point out a real problem, sometimes they're just useful when initially developing a feature to track program flow but lose utility once the feature lands. Generally the sheer volume just makes it hard to find any real issues. *What does the tool do?* - *Reporting* - Downloads and parses test results to present a summary of the most common warnings - *Bisecting* - Helps narrow down when a warning showed up - *Filing* - Automates the process of filing a detailed bug in the appropriate component *How do I use it?* Examples and extended help are available in the github repo <https://github.com/EricRahm/log-spam-hell#basic-usage> as well as via the command line mach logspam --help A few quick examples: - Report on the latest linux build on central: ./mach logspam report latest - Report on try run: ./mach logspam report --repo try 2f23de3f6837d7fa7102fd8affc65f1d296f9e11 - Specific details of a warning found in that try run including which test suites and tests it shows up in: ./mach logspam report --repo try \ 2f23de3f6837d7fa7102fd8affc65f1d296f9e11 \ "WARNING: Shouldn't call SchedulePaint in a detached pres context: file layout/generic/nsIFrame.cpp, line 6868" *What's next?* If folks want to improve the tool I'm happy to land patches in my repo, or if someone wants to support it officially in the mozilla repo I'm happy to transfer ownership. -e _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
