imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https.html Description: This test is flaky failing on Mac wk2 Release History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fwebrtc%2FRTCPeerConnection-iceConnectionState.https.html&platform=mac&limit=50000&style=release Diff: --- /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https-expected.txt +++ /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https-actual.txt @@ -1,3 +1,5 @@ + +Harness Error (FAIL), message = Unhandled rejection: The object is in an invalid state. PASS Initial iceConnectionState should be new PASS Closing the connection should set iceConnectionState to closed
<rdar://problem/59785430>
The oldest diff that I was able to load, r254862, matched the diff in the original post. I have marked this test as failing while this issue is investigated. https://trac.webkit.org/changeset/257387/webkit
I can reproduce this issue with r257468 using the command below. run-webkit-tests imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https.html --iterations 3000 --exit-after-n-failures 5 -f --force --exit-after-n-failures 5 [160/3000] imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https.html failed unexpectedly (text diff) [204/3000] imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https.html failed unexpectedly (text diff) [240/3000] imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https.html failed unexpectedly (text diff) [328/3000] imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https.html failed unexpectedly (text diff) [538/3000] imported/w3c/web-platform-tests/webrtc/RTCPeerConnection-iceConnectionState.https.html failed unexpectedly (text diff) Exiting early after 5 failures. 535 tests run. 530 tests ran as expected, 5 didn't (2465 didn't run):
Probably a timing issue we should fix by updating the test
*** This bug has been marked as a duplicate of bug 231223 ***