261005 2023-08-31 17:28:44 -0700 [ macOS wk2 ] swipe/pushState-cached-back-swipe.html is a flaky timeout / text failure. 2025-03-08 02:47:07 -0800 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 282126 InRadar P2 Normal --- 1 ben_schwartz webkit-unassigned thorton webkit-bot-watchers-bugzilla webkit-bug-importer oldest_to_newest 1974879 0 ben_schwartz 2023-08-31 17:28:44 -0700 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. 1974880 1 webkit-bug-importer 2023-08-31 17:28:55 -0700 <rdar://problem/114797952> 1974882 2 ben_schwartz 2023-08-31 17:31:13 -0700 Clarifying: 266683@main is the first visible failure on the flakiness dashboard. 1974884 3 ews-feeder 2023-08-31 17:43:13 -0700 Test gardening commit 267534@main (e803ed36e11d): <https://commits.webkit.org/267534@main> Reviewed commits have been landed. Closing PR #17316 and removing active labels. 2101631 4 thorton 2025-03-08 02:47:07 -0800 Going to give all of the swipe tests new life in bug 282126. *** This bug has been marked as a duplicate of bug 282126 ***