NEW 217621
REGRESSION: [ Mac & iOS ] media/video-buffering-allowed.html is flaky timeout
https://bugs.webkit.org/show_bug.cgi?id=217621
Summary REGRESSION: [ Mac & iOS ] media/video-buffering-allowed.html is flaky timeout
Truitt Savell
Reported 2020-10-12 10:56:38 PDT
media/video-buffering-allowed.html This test is flakily timeout out on MacOS History: https://results.webkit.org/?suite=layout-tests&test=media%2Fvideo-buffering-allowed.html
Attachments
Radar WebKit Bug Importer
Comment 1 2020-10-12 10:57:00 PDT
Truitt Savell
Comment 2 2020-10-12 16:16:36 PDT
I was able to reproduce this timeout using command: run-webkit-tests --iterations 2000 --exit-after-n-failures 1 --exit-after-n-crashes-or-timeouts 1 --debug-rwt-logging --no-retry --force --no-build -f media/video-buffering-allowed.html
Truitt Savell
Comment 3 2020-11-09 15:28:26 PST
Marked this test as timing out in https://trac.webkit.org/changeset/269607/webkit
Ryan Haddad
Comment 4 2020-12-23 13:21:37 PST
(In reply to Truitt Savell from comment #3) > Marked this test as timing out in > https://trac.webkit.org/changeset/269607/webkit This was added to Rosetta expectations, but as far as I can tell this has always impacted macOS generally. Fixed expectation in r271077.
ayumi_kojima
Comment 5 2021-07-23 16:19:18 PDT
The flaky timeout is also seen on iOS 14 E Simulator Release. I was able to reproduce the timeout using: un-webkit-tests --iterations 2000 --exit-after-n-failures 1 --exit-after-n-crashes-or-timeouts 1 --ios-simulator --release --no-retry --force --no-build -f media/video-buffering-allowed.html Updated test expectations: https://trac.webkit.org/changeset/280270/webkit
Dawn Morningstar
Comment 6 2024-08-19 13:06:59 PDT
This test is also a flaky timeout on iOS debug not just release.
Dawn Morningstar
Comment 7 2024-08-19 13:12:57 PDT
EWS
Comment 8 2024-08-19 13:15:06 PDT
Test gardening commit 282455@main (f4cf3cda9474): <https://commits.webkit.org/282455@main> Reviewed commits have been landed. Closing PR #32409 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.