Bug 261005
| Summary: | [ macOS wk2 ] swipe/pushState-cached-back-swipe.html is a flaky timeout / text failure. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ben Schwartz <ben_schwartz> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | thorton, webkit-bot-watchers-bugzilla, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ben Schwartz
swipe/pushState-cached-back-swipe.html
This test is a flaky timeout on wk2 on macOS, and specifically a flaky failure on release.
HISTORY:
https://results.webkit.org/?suite=layout-tests&test=swipe%2FpushState-cached-back-swipe.html
TEXT DIFF:
willEndSwipe
didEndSwipe
didRemoveSwipeSnapshot
+Failure. Because we're using the page cache, it shouldn't be long between the gesture completing and the snapshot being removed. (expected: 1000, actual: 1036)
DIFF URL:
https://build.webkit.org/results/Apple-Ventura-Release-AppleSilicon-WK2-Tests/267071@main%20(4533)/swipe/pushState-cached-back-swipe-pretty-diff.html
REPRODUCIBILITY:
I was able to reproduce this bug on macOS Ventura (13.5, 22G74/arm64) using the following command:
run-webkit-tests --clobber-old-results --verbose --iterations 1000 --child-processes 100 -f --exit-after-n-failures 1 swipe/pushState-cached-back-swipe.html
REGRESSION:
I was unable to identify a regression point; however, the first failure appears to have occurred at 266683@main on macOS Monterey (x86_64) wk2 release.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/114797952>
Ben Schwartz
Clarifying: 266683@main is the first visible failure on the flakiness dashboard.
EWS
Test gardening commit 267534@main (e803ed36e11d): <https://commits.webkit.org/267534@main>
Reviewed commits have been landed. Closing PR #17316 and removing active labels.
Tim Horton
Going to give all of the swipe tests new life in bug 282126.
*** This bug has been marked as a duplicate of bug 282126 ***