| Summary: | [ wk2 ] media/presentationmodechanged-fired-once.html is a flakey timeout | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Robert Jenner <jenner> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | peng.liu6, webkit-bot-watchers-bugzilla, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Robert Jenner
2021-04-15 17:02:20 PDT
The timeouts are not easy to reproduce, but I have been able to reproduce it at BigSur Debug ToT using the following: 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 --debug media/presentationmodechanged-fired-once.html The timeout does not reproduce every time the above test is run. But it's the only way I've had any success at all with reproducing the timeout. I will attempt to discover a regression point, but given the flakiness of this test, I might not be able to. But we will see. Updated test expectation to Pass Timeout here while test is reviewed: https://trac.webkit.org/changeset/276163/webkit I have not been able to reliably reproduce the timeouts. For this reason, I cannot discover a regression point. Updated expectations for iOS here as well: https://trac.webkit.org/changeset/276165/webkit |