RESOLVED DUPLICATE of bug 231223 Bug 230157
Regression (r279461): [ MacOS wk2 & iOS Release ] imported/w3c/web-platform-tests/webrtc/no-media-call.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=230157
Summary Regression (r279461): [ MacOS wk2 & iOS Release ] imported/w3c/web-platform-t...
ayumi_kojima
Reported 2021-09-10 09:27:42 PDT
imported/w3c/web-platform-tests/webrtc/no-media-call.html Is a flaky failure on MacOS (Release & Debug) and iOS Release. History: https://results.webkit.org/?suite=layout-tests&test=imported/w3c/web-platform-tests/webrtc/no-media-call.html The flaky failure is also showing up on EWS as a flaky test at https://ews-build.webkit.org/#/builders/51/builds/20702. Result page: https://build.webkit.org/results/Apple-iOS-14-Simulator-Release-WK2-Tests/r282265%20(3155)/results.html Diff: --- /Volumes/Data/worker/ios-simulator-14-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/webrtc/no-media-call-expected.txt +++ /Volumes/Data/worker/ios-simulator-14-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/webrtc/no-media-call-actual.txt @@ -2,5 +2,5 @@ PASS Can set up a basic WebRTC call with no data. iceConnectionState info -First: connected +First: completed Second: connected
Attachments
Radar WebKit Bug Importer
Comment 1 2021-09-10 09:38:49 PDT
ayumi_kojima
Comment 2 2021-09-10 09:39:11 PDT
ayumi_kojima
Comment 3 2021-09-13 11:30:43 PDT
I was able to reproduce the failure on BigSur using run-webkit-tests --iterations 100 --exit-after-n-failures 1 --force imported/w3c/web-platform-tests/webrtc/no-media-call.html. The failure seems to have started at https://trac.webkit.org/changeset/279461/webkit Also, looking at the history, recently the test has started consistently failing at around https://trac.webkit.org/changeset/282281/webkit
youenn fablet
Comment 4 2021-09-17 06:31:00 PDT
Test is no longer flaky according to bots after moving to standardised ice connection state callback.
youenn fablet
Comment 5 2021-10-05 02:48:16 PDT
*** This bug has been marked as a duplicate of bug 231223 ***
Note You need to log in before you can comment on or make changes to this bug.