Closed Bug 1360908 Opened 7 years ago Closed 6 years ago

Intermittent dom/media/tests/mochitest/test_peerConnection_twoAudioStreams.html | Assertion count 1 is greater than expected range 0-0 assertions.

Categories

(Core :: WebRTC, defect, P5)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
fennec + ---

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

gbrown: The log doesn't contain the actual assertion message. Do you know what I'm doing wrong to not have it in the log?
tracking-fennec: --- → ?
Flags: needinfo?(gbrown)
I expect assertion messages to only be in the logcat -- not the main test log.

But in this case, I don't see the assertion message in the logcat. I also can't find "test_peerConnection_twoAudioStreams.html" in the logcat. Odd, right?

I do see a bunch of messages like this:

04-29 17:17:56.883 I/chatty  ( 8617): uid=10078(org.mozilla.fennec) Gecko expire 422 lines

which I haven't seen before. Is this telling us that something is trimming logcat of what it considers overly verbose messages?
Flags: needinfo?(gbrown)
Yep, you are right.

http://stackoverflow.com/questions/34587273/android-logcat-logs-chatty-module-line-expire-message

has a suggestion

adb logcat -P ""

https://developer.android.com/studio/command-line/logcat.html has more information on setting the white and black lists for messages.

Filed bug 1360920 for autophone/adb. We should also do this for devicemanager when we have a solution.
Depends on: 1360920
Rank: 25
Priority: -- → P2
tracking-fennec: ? → +
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Bulk priority update of open intermittent test failure bugs. 

P3 => P5

https://bugzilla.mozilla.org/show_bug.cgi?id=1381960
Priority: P3 → P5
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.