[Webkit-unassigned] [Bug 214286] New: (r264202) [ Mac iOS WK2 ] imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-connectionState.https.html

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=214286

            Bug ID: 214286
           Summary: (r264202) [ Mac iOS WK2 ]
                    imported/w3c/web-platform-tests/webrtc/RTCPeerConnecti
                    on-connectionState.https.html
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: tsavell at apple.com

imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-connectionState.https.html

This test has been flaky sense introduction in https://trac.webkit.org/changeset/264202/webkit

History:
https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fwebrtc%2FRTCPeerConnection-connectionState.https.html

Diff:
--- /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-connectionState.https-expected.txt
+++ /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-connectionState.https-actual.txt
@@ -3,7 +3,7 @@
 PASS Closing the connection should set connectionState to closed 
 PASS connection with one data channel should eventually have connected connection state 
 FAIL connection with one data channel should eventually have transports in connected state undefined is not an object (evaluating 'sctpTransport.transport')
-FAIL connectionState remains new when not adding remote ice candidates assert_equals: expected "new" but got "checking"
+FAIL connectionState remains new when not adding remote ice candidates assert_equals: expected "new" but got "completed"
 PASS connectionState transitions to connected via connecting 
 PASS Closing a PeerConnection should not fire connectionstatechange event 


I was able to repro a failure but it was a different diff result. I reproduced using run-webkit-tests imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-connectionState.https.html --iterations 1000 -f --exit-after-n-failures 1

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200713/85da3737/attachment.htm>