NEW244601
Test addition (253230@main): [ macOS wk1 ] http/tests/media/fairplay/fps-mse-unmuxed-key-renewal.html is a flaky failure 
https://bugs.webkit.org/show_bug.cgi?id=244601
Summary Test addition (253230@main): [ macOS wk1 ] http/tests/media/fairplay/fps-mse-...
Karl Rackler
Reported 2022-08-31 07:11:51 PDT
Description: http/tests/media/fairplay/fps-mse-unmuxed-key-renewal.html This test was added at 253230@main and has been a consistent failure since. REPRODUCTION STEPS I can reproduce this on 253979@main ToT. Command: run-webkit-tests --debug -1 --exit-after-n-failures 1 --exit-after-n-crashes-or-timeouts 1 --iterations 50 -f --no-retry http/tests/media/fairplay/fps-mse-unmuxed-key-renewal.html Result: Regressions: Unexpected text-only failures (1) http/tests/media/fairplay/fps-mse-unmuxed-key-renewal.html [ Failure ] History: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fmedia%2Ffairplay%2Ffps-mse-unmuxed-key-renewal.html&platform=mac&flavor=wk1&architecture=x86_64&limit=50000 Diff: --- /Volumes/Data/worker/Apple-Monterey-Debug-WK1-Tests/build/layout-test-results/http/tests/media/fairplay/fps-mse-unmuxed-key-renewal-expected.txt +++ /Volumes/Data/worker/Apple-Monterey-Debug-WK1-Tests/build/layout-test-results/http/tests/media/fairplay/fps-mse-unmuxed-key-renewal-actual.txt @@ -1,3 +1,4 @@ +set AppID to 1 PROMISE: requestMediaKeySystemAccess resolved PROMISE: createMediaKeys resolved
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2022-08-31 07:12:07 PDT
<rdar://problem/99381606>
Karl Rackler
Comment 2 2022-08-31 07:21:38 PDT
I have marked this test as a consistent failure while this issue is investigated.
Karl Rackler
Comment 3 2022-08-31 07:22:34 PDT
[ Update ] This only seems to be affecting macOS wk1 on x86_64.
EWS
Comment 4 2022-08-31 07:30:07 PDT
Test gardening commit 253983@main (4236b8f72aae): <https://commits.webkit.org/253983@main> Reviewed commits have been landed. Closing PR #3850 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.