Hi, Mochitest (M1, M2, M3, M4, M5, and M-oth on TBPL) logging has seen several changes over the past couple of weeks. The intent of these changes is to reduce the runtime of the tests, particularly for tests which produce many messages, and reduce the log file sizes. The current status on inbound, post-bug 977198 landing, is:
- Tests with no failures (all TEST-PASS or TEST-KNOWN-FAIL) produce only TEST-START and TEST-END messages. This is similar to what xpcshell has been doing for some time now. - If there is a TEST-FAIL or a TEST-UNEXPECTED-PASS, then the failure itself is logged, along with some number of messages (currently capped at 100) since the start of the test or the last failure. The intent here was to provide most of the benefits of suppressing messages while still showing some record of what the test was doing prior to the failure. - If you run a single test locally, then all the messages produced by the test will be shown. (Please note that these rules do not apply to browser-chrome and metro tests, due to the different logging framework they use. Hooray for consistency.) If you require more context for your TEST-FAILs, then you may call SimpleTest.requestCompleteLog() in your test and all messages after the call will be displayed. Please treat this as a debugging aid for Try or for intermittent oranges; it shouldn't be necessary to have SimpleTest.requestCompleteLog() calls lying around in our test suite. For those interested in the nuts and bolts of the changes, you can refer to https://bugzilla.mozilla.org/show_bug.cgi?id=937181 and its dependent/blocking bugs. Thanks, -Nathan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
