Closed Bug 1180968 Opened 4 years ago Closed 2 years ago

Intermittent test_peerConnection_certificates.html | Test timed out.

Categories

(Core :: WebRTC, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Blocking Flags:

People

(Reporter: KWierso, Assigned: mt)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Attachments

(1 file, 2 obsolete files)

16:12:26 INFO - 4218 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_certificates.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
16:12:26 INFO - 4219 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_certificates.html | Should have RTP stats for track {4c1a1406-6215-4efe-9c55-cb3e0acfac23}
16:12:26 INFO - 4220 INFO Track {4c1a1406-6215-4efe-9c55-cb3e0acfac23} has 0 outboundrtp RTP packets.
16:12:26 INFO - 4221 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_certificates.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
16:12:26 INFO - 4222 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_certificates.html | Should have RTP stats for track {4c1a1406-6215-4efe-9c55-cb3e0acfac23}
16:12:26 INFO - 4223 INFO Track {4c1a1406-6215-4efe-9c55-cb3e0acfac23} has 0 outboundrtp RTP packets.
16:12:26 INFO - 4224 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_certificates.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
16:12:26 INFO - 4225 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_certificates.html | Should have RTP stats for track {4c1a1406-6215-4efe-9c55-cb3e0acfac23}
16:12:26 INFO - 4226 INFO Track {4c1a1406-6215-4efe-9c55-cb3e0acfac23} has 0 outboundrtp RTP packets.
16:12:26 INFO - 4227 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_certificates.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
16:12:26 INFO - 4228 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_certificates.html | Should have RTP stats for track {4c1a1406-6215-4efe-9c55-cb3e0acfac23}
16:12:26 INFO - 4229 INFO Track {4c1a1406-6215-4efe-9c55-cb3e0acfac23} has 0 outboundrtp RTP packets.
16:12:26 INFO - 4230 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_certificates.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
16:12:26 INFO - 4231 INFO TEST-UNEXPECTED-FAIL | dom/media/tests/mochitest/test_peerConnection_certificates.html | Test timed out. - expected PASS
16:12:26 INFO - 4232 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_certificates.html | Should have RTP stats for track {4c1a1406-6215-4efe-9c55-cb3e0acfac23}
16:12:26 INFO - 4233 INFO Track {4c1a1406-6215-4efe-9c55-cb3e0acfac23} has 0 outboundrtp RTP packets.
16:12:26 INFO - 4234 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_certificates.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
16:12:26 INFO - 4235 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_certificates.html | Should have RTP stats for track {4c1a1406-6215-4efe-9c55-cb3e0acfac23}
16:12:26 INFO - 4236 INFO Track {4c1a1406-6215-4efe-9c55-cb3e0acfac23} has 0 outboundrtp RTP packets.
16:12:26 INFO - 4237 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_certificates.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
Martin - Is this due to your recent checkin?
backlog: --- → webRTC+
Rank: 23
Flags: needinfo?(martin.thomson)
Priority: -- → P2
Yes indeed.  The error here is one party is complaining about a certificate that it sees and the other receiving a bad certificate alert.

That this has only appeared in pgo builds so far worries me.  I'll keep an eye on this.
Assignee: nobody → martin.thomson
Flags: needinfo?(martin.thomson)
(In reply to Martin Thomson [:mt:] from comment #5)
> That this has only appeared in pgo builds so far worries me.  I'll keep an
> eye on this.

Not entirely PGO-only, but extremely frequent nonetheless :(
Keywords: leave-open
[Mass Closure] Closing Intermittent as a one off
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
Still need to enable the test.  No intermittents yet, but only about 60 runs so far.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Bug 1180968 - Enable WebRTC certificates test, r?jib
Attachment #8675203 - Flags: review?(jib)
Bug 1215519 - Switch to DOMTimeStamp for RTCCertificate, r?bz
Attachment #8675204 - Flags: review?(bzbarsky)
Comment on attachment 8675204 [details]
MozReview Request: Bug 1215519 - Switch to DOMTimeStamp for RTCCertificate, r?bz

Bad reviewboard.
Attachment #8675204 - Flags: review?(bzbarsky)
Comment on attachment 8675203 [details]
MozReview Request: Bug 1180968 - Enable WebRTC certificates test, r?jib

Not until I'm more confident that this is OK.
Attachment #8675203 - Flags: review?(jib)
Jan-Ivar, do you think that this is worth re-enabling again?  Tim Taubert made some changes to the threading using by WebCrypto and I think that's changed things.  See the PGO build in comment 105.
Flags: needinfo?(jib)
I can't access the logs in comment 105 for some reason (perhaps due to the recent ftp move?) I suspect I don't have a strong opinion, other than it's nice to have tests enabled.
Flags: needinfo?(jib)
Attachment #8675204 - Attachment is obsolete: true
Attachment #8675203 - Attachment is obsolete: true
Attached patch bug1180968.patchSplinter Review
I can't reproduce the problem any more.  >100 attempts on PGO builds and all pass.  In other positive news, I'm seeing far fewer random failures on WebRTC mochitests.
Attachment #8677057 - Flags: review?(jib)
Attachment #8677057 - Flags: review?(jib) → review+
Keywords: checkin-needed
Backed out in https://hg.mozilla.org/integration/mozilla-inbound/rev/a2e2d5b8b3f7 - we didn't much bother to actually run tests on your push itself, so it only got one, https://treeherder.mozilla.org/logviewer.html#?job_id=16065083&repo=mozilla-inbound, but the next push had timeouts in Linux32 opt, Linux32 debug straight and e10s, Linux64 opt, ASan, and Linux64 debug e10s.
Blocks: 1321547
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Status: REOPENED → RESOLVED
Closed: 4 years ago2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.