imported/w3c/web-platform-tests/webrtc/simplecall-no-ssrcs.https.html This flaky failure appears to have started around r278084 - r278086. Will investigate further and update. History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fwebrtc%2Fsimplecall-no-ssrcs.https.html --- /Volumes/Data/worker/bigsur-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/webrtc/simplecall-no-ssrcs.https-expected.txt +++ /Volumes/Data/worker/bigsur-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/webrtc/simplecall-no-ssrcs.https-actual.txt @@ -1,4 +1,4 @@ - +332162.230 189 -------- dropped: AFTER encoding -------- - -1/ -1 55.6 0/ 0 1 0/ 0 -- PASS Can set up a basic WebRTC call without announcing ssrcs.
<rdar://problem/79971611>
Reproduced failure in r278649 DEBUG using rwt --root /Volumes/Data/Builds/278649 --debug --iterations 500 --exit-after-n-failures 2 imported/w3c/web-platform-tests/webrtc/simplecall-no-ssrcs.https.html. Unable to reproduce in release version. Unable to reproduce in r278651 Debug or r278649 Debug.
(In reply to Eric Hutchison from comment #2) > Reproduced failure in r278649 DEBUG using rwt --root > /Volumes/Data/Builds/278649 --debug --iterations 500 --exit-after-n-failures > 2 imported/w3c/web-platform-tests/webrtc/simplecall-no-ssrcs.https.html. > Unable to reproduce in release version. Unable to reproduce in r278651 Debug > or r278649 Debug. CORRECTION: Reproduced in r278650 Debug version. Unable to reproduce in r278649 Debug or r278651 debug. Test run: run-webkit-test --debug --iterations 500 --exit-after-n-failures 2 imported/w3c/web-platform-tests/webrtc/simplecall-no-ssrcs.https.html
Created attachment 432629 [details] Patch
Created attachment 432630 [details] TestExpectations update
Comment on attachment 432630 [details] TestExpectations update Clearing flags on attachment: 432630 Committed r279433 (239292@main): <https://commits.webkit.org/239292@main>
I was getting an unexpected result due to a local issue. I am unable to reproduce this test issue with current builds.