NEW 206698
[iOS wk2] editing/caret/ios/fixed-caret-position-after-scroll.html flaky failing 
https://bugs.webkit.org/show_bug.cgi?id=206698
Summary [iOS wk2] editing/caret/ios/fixed-caret-position-after-scroll.html flaky failing
Jason Lawrence
Reported 2020-01-23 13:54:27 PST
editing/caret/ios/fixed-caret-position-after-scroll.html Description: The test is flaky failing on iOS wk2. History: https://results.webkit.org/?suite=layout-tests&test=editing%2Fcaret%2Fios%2Ffixed-caret-position-after-scroll.html Diff: --- /Volumes/Data/slave/ios-simulator-13-release-tests-wk2/build/layout-test-results/editing/caret/ios/fixed-caret-position-after-scroll-expected.txt +++ /Volumes/Data/slave/ios-simulator-13-release-tests-wk2/build/layout-test-results/editing/caret/ios/fixed-caret-position-after-scroll-actual.txt @@ -3,10 +3,11 @@ PASS initialCaretRect.width is 3 PASS initialCaretRect.height is 15 PASS finalCaretRect.left is 6 -PASS finalCaretRect.top is 4977 +FAIL finalCaretRect.top should be 4977. Was 21. PASS finalCaretRect.width is 3 PASS finalCaretRect.height is 15 PASS successfullyParsed is true +Some tests failed. TEST COMPLETE
Attachments
Update Test Expectations (1.32 KB, patch)
2020-01-28 10:16 PST, Jason Lawrence 		no flags
DetailsFormatted DiffDiff
Update Test Expectations (1.32 KB, patch)
2020-01-28 10:20 PST, Jason Lawrence 		no flags
DetailsFormatted DiffDiff
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2020-01-23 13:54:48 PST
<rdar://problem/58847126>
Jason Lawrence
Comment 2 2020-01-28 10:16:29 PST
Created attachment 389026 [details] Update Test Expectations
Jason Lawrence
Comment 3 2020-01-28 10:20:56 PST
Created attachment 389027 [details] Update Test Expectations
Truitt Savell
Comment 4 2020-01-28 10:22:47 PST
Comment on attachment 389027 [details] Update Test Expectations Clearing flags on attachment: 389027 Committed r255256: <https://trac.webkit.org/changeset/255256>
Jason Lawrence
Comment 5 2020-01-28 13:25:44 PST
I was not able to reproduce this issue by running a large number of WebKit test iterations.
Note You need to log in before you can comment on or make changes to this bug.