Filed by: bclary [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=97213551&repo=mozilla-central https://autophone.s3.amazonaws.com/v1/task/S2ynEpDuR8aW8RrZXdcWdA/runs/0/artifacts/public/build/autophone-mochitest-dom-media-tests-mochitests-dom-media-tests-settings-debug.ini-1-nexus-6p-5-3337ec58-1656-46f2-873e-2072dcf7cc9f-autophone.log

Hi Bob, sorry if this is a dumb question but how can we get more log detail on the actual assert that failed? > 2017-05-07 22:28:43,138 nexus-6p-5 INFO UnitTestJob 20170508031158 debug mochitest-dom-media-tests 210 INFO TEST-START | dom/media/tests/mochitest/test_peerConnection_stats.html > 2017-05-07 22:28:43,138 nexus-6p-5 INFO UnitTestJob 20170508031158 debug mochitest-dom-media-tests 211 INFO TEST-OK | dom/media/tests/mochitest/test_peerConnection_stats.html | took 13953ms > 2017-05-07 22:28:43,138 nexus-6p-5 INFO UnitTestJob 20170508031158 debug mochitest-dom-media-tests 212 INFO TEST-UNEXPECTED-ERROR | dom/media/tests/mochitest/test_peerConnection_stats.html | Assertion count 1 is greater than expected range 0-0 assertions. > 2017-05-07 22:28:43,138 nexus-6p-5 INFO UnitTestJob 20170508031158 debug mochitest-dom-media-tests {u'max_asserts': 0, u'assertions': 1, u'min_asserts': 0}

Not at dumb question at all. I had the same one. Hmmm, maybe... It seems the assertion message is written to the logcat which is dropping the messages when the rate gets too high. See Bug 1360920. I'll try to get to it as soon as I can.

This is a P1 bug without an assignee. P1 are bugs which are being worked on for the current release cycle/iteration/sprint. If the bug is not assigned by Monday, 28 August, the bug's priority will be reset to '--'.

Mass change P1->P2 to align with new Mozilla triage process