If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Intermittent dom/media/tests/mochitest/test_peerConnection_basicAudioPcmaPcmuOnly.html | PeerConnectionWrapper (pcLocal): legal ICE state transition from connected to failed

RESOLVED FIXED in Firefox 51

Status

()

Core
WebRTC
P2
normal
Rank:
25
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: Treeherder Bug Filer, Assigned: drno)

Tracking

({intermittent-failure})

unspecified
mozilla52
intermittent-failure
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(firefox50 unaffected, firefox51 fixed, firefox52 fixed)

Details

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(1 attachment)

(Reporter)

Description

a year ago
treeherder
Filed by: philringnalda [at] gmail.com

https://treeherder.mozilla.org/logviewer.html#?job_id=33539266&repo=mozilla-inbound

https://queue.taskcluster.net/v1/task/FzC_5RfySxiWnixpAz7FXg/runs/0/artifacts/public%2Flogs%2Flive_backing.log

https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/FzC_5RfySxiWnixpAz7FXg/runs/0/artifacts/public%2Flogs%2Flive_backing.log&only_show_unexpected=1
Blocks: 1271585
Nils - 6 failures since I landed.  Should we disable this one as well?  Should we do something to bump timeouts on android emulator (perhaps a longer-term thing, if we care about emulator - though might help on VMs too)
Rank: 25
Flags: needinfo?(drno)
Priority: -- → P2
(Assignee)

Comment 2

a year ago
Hmm this is ICE consent freshness failing on a super simple test case (audio only). I'm worried that if we disable this one we will just continue disabling all PC mochitests on Android emu debug.
The only thing which makes this test special is that it's suppose to use PCMA/PMCU, so we might have more network traffic compared to Opus on the network (?), but less CPU overhead.

Emulator stats at the end of one of the test runs:
 TinderboxPrint: CPU idle<br/>11,268.4 (74.8%)
 TinderboxPrint: CPU user<br/>3,739.6 (24.8%)

Daniel: is this test already covered by the Autophone tests?
Flags: needinfo?(drno) → needinfo?(dminor)

Comment 3

a year ago
20 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 15
* autoland: 5

Platform breakdown:
* android-4-3-armv7-api15: 20

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-08-10&endday=2016-08-10&tree=all
We're only running the webrtc job on mozilla-central at the moment. I need to fix Bug 1277653 before we can schedule the tests on mozilla-inbound / autoland. I'm addressing review comments on that bug now.
Flags: needinfo?(dminor)

Comment 5

a year ago
75 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 49
* autoland: 14
* fx-team: 8
* try: 3
* mozilla-central: 1

Platform breakdown:
* android-4-3-armv7-api15: 75

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-08-08&endday=2016-08-14&tree=all

Comment 6

a year ago
24 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 12
* autoland: 7
* fx-team: 4
* mozilla-central: 1

Platform breakdown:
* android-4-3-armv7-api15: 24

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-08-19&endday=2016-08-19&tree=all

Comment 7

a year ago
72 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 34
* autoland: 27
* fx-team: 8
* mozilla-central: 2
* try: 1

Platform breakdown:
* android-4-3-armv7-api15: 72

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-08-15&endday=2016-08-21&tree=all

Comment 8

a year ago
17 automation job failures were associated with this bug yesterday.

Repository breakdown:
* autoland: 9
* mozilla-inbound: 6
* fx-team: 2

Platform breakdown:
* android-4-3-armv7-api15: 17

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-08-23&endday=2016-08-23&tree=all

Comment 9

a year ago
71 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* autoland: 32
* mozilla-inbound: 29
* fx-team: 6
* try: 3
* mozilla-central: 1

Platform breakdown:
* android-4-3-armv7-api15: 71

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-08-22&endday=2016-08-28&tree=all
19 automation job failures were associated with this bug yesterday.

Repository breakdown:
* autoland: 9
* mozilla-inbound: 8
* try: 2

Platform breakdown:
* android-4-3-armv7-api15: 19

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-08-31&endday=2016-08-31&tree=all
70 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* autoland: 28
* mozilla-inbound: 26
* mozilla-central: 7
* fx-team: 5
* try: 4

Platform breakdown:
* android-4-3-armv7-api15: 70

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-08-29&endday=2016-09-04&tree=all
53 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 23
* autoland: 21
* fx-team: 6
* mozilla-central: 3

Platform breakdown:
* android-4-3-armv7-api15: 53

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-05&endday=2016-09-11&tree=all
16 automation job failures were associated with this bug yesterday.

Repository breakdown:
* autoland: 6
* fx-team: 5
* mozilla-inbound: 4
* mozilla-central: 1

Platform breakdown:
* android-4-3-armv7-api15: 16

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-12&endday=2016-09-12&tree=all
18 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 12
* fx-team: 4
* try: 1
* autoland: 1

Platform breakdown:
* android-4-3-armv7-api15: 18

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-14&endday=2016-09-14&tree=all
16 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 7
* autoland: 5
* fx-team: 3
* try: 1

Platform breakdown:
* android-4-3-armv7-api15: 15
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-16&endday=2016-09-16&tree=all
79 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 34
* autoland: 23
* fx-team: 14
* mozilla-central: 5
* try: 3

Platform breakdown:
* android-4-3-armv7-api15: 78
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-12&endday=2016-09-18&tree=all
(Assignee)

Comment 17

a year ago
Darn it the Linux failures are false reports. On Linux it never failed on the PcmaPcmu test.

Which leaves us with ARM only. Interestingly the second peer connection needs about 1 min until it also disconnect after the first switched to failed.
As this should use fixed rate codecs only I really don't see another way then disabling the test on ARM debug for now and then monitor what will fail next.
17 automation job failures were associated with this bug yesterday.

Repository breakdown:
* autoland: 8
* mozilla-inbound: 7
* mozilla-central: 1
* fx-team: 1

Platform breakdown:
* android-4-3-armv7-api15: 17

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-21&endday=2016-09-21&tree=all
21 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 11
* autoland: 8
* mozilla-aurora: 1
* fx-team: 1

Platform breakdown:
* android-4-3-armv7-api15: 21

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-22&endday=2016-09-22&tree=all
17 automation job failures were associated with this bug yesterday.

Repository breakdown:
* autoland: 7
* mozilla-inbound: 5
* fx-team: 2
* try: 1
* mozilla-central: 1
* mozilla-aurora: 1

Platform breakdown:
* android-4-3-armv7-api15: 17

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-23&endday=2016-09-23&tree=all
(Assignee)

Comment 21

a year ago
{
  "outbound_rtcp_audio_0": {
    "ssrc": "2300128555",
    "bytesReceived": 23840,
    "jitter": 0.447,
    "mozRtt": 1,
    "packetsLost": 0,
    "packetsReceived": 149
  },
  "outbound_rtp_audio_0": {
    "ssrc": "2300128555",
    "bytesSent": 84360,
    "packetsSent": 444
  },

I think this clearly shows the receiver is hopelessly behind on the RTP packets. I guess there is little we do about it, besides deactivating the test on ARM.
Make we wonder if we should do some performance evaluation to figure out where these damn emulator spend all their time.

The other idea which came to my mind is that our tests could put up warnings based on the RTCP information I just posted above indicating that the machine appears to be overloaded.
75 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 32
* autoland: 31
* fx-team: 6
* mozilla-central: 3
* mozilla-aurora: 2
* try: 1

Platform breakdown:
* android-4-3-armv7-api15: 75

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-19&endday=2016-09-25&tree=all
Comment hidden (mozreview-request)

Comment 24

a year ago
mozreview-review
Comment on attachment 8794715 [details]
Bug 1293531: disable PcmaPcmu test on Android.

https://reviewboard.mozilla.org/r/81052/#review79682

We will still run this on Autophone.
Attachment #8794715 - Flags: review?(dminor) → review+

Comment 25

a year ago
Pushed by drno@ohlmeier.org:
https://hg.mozilla.org/integration/autoland/rev/6a20fed1e079
disable PcmaPcmu test on Android. r=dminor

Comment 26

a year ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/6a20fed1e079
Status: NEW → RESOLVED
Last Resolved: a year ago
status-firefox52: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
Assignee: nobody → drno
status-firefox50: --- → unaffected
status-firefox51: --- → affected

Comment 27

a year ago
bugherderuplift
https://hg.mozilla.org/releases/mozilla-aurora/rev/bed31970262c
status-firefox51: affected → fixed
Flags: in-testsuite-
10 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 7
* autoland: 2
* mozilla-central: 1

Platform breakdown:
* android-4-3-armv7-api15: 10

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1293531&startday=2016-09-26&endday=2016-10-02&tree=all
You need to log in before you can comment on or make changes to this bug.