Myself and others on Automation and Tools have undertaken an effort to convert our test harnesses to use structured logging. We are making this conversion to allow our testing infrastructure to move away from regex based log parsing and to expose more useful log data (with a focus on test results as JSON) to a wider variety of consumers. Ahmed Kachkach, an intern with the A*Team this summer posted earlier with an update about Mochitests. I'm following up here with pointers to more information.
Documentation for the python logging library we're building on (mozlog) is available on readthedocs[1] and includes some examples if you're curious about how this works. I've written up a short wiki page [2] including some background on the project, and we’ve been using bug 916295 [3] to track progress. We're intending to provide a foundation for future tools and infrastructure improvements without disrupting familiar workflows or breaking compatibility with existing tools, so the changes will be largely unobtrusive at this stage. If you have trouble running tests locally or observe undesired changes to test harness output, this could be an unintended side effect of this work that needs to be addressed. Ping me (chmanchester) in #ateam if you have any questions. Bugs/features for mozlog should be filed in Testing :: Mozbase. [1] http://mozbase.readthedocs.org/en/latest/mozlog_structured.html [2] https://wiki.mozilla.org/Auto-tools/Projects/Structured_Logging [3] https://bugzilla.mozilla.org/show_bug.cgi?id=916295 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
