RESOLVED FIXED 191680
[GTK] Two pasteboard tests are flaky
https://bugs.webkit.org/show_bug.cgi?id=191680
Summary [GTK] Two pasteboard tests are flaky
Miguel Gomez
Reported 2018-11-15 06:43:21 PST
editing/pasteboard/copy-paste-first-line-in-textarea.html [ Failure Pass ] Most of the time the test passes but every now and then fails in the first run. The diff when it happen is: --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/editing/pasteboard/copy-paste-first-line-in-textarea-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/editing/pasteboard/copy-paste-first-line-in-textarea-actual.txt @@ -1,3 +1,3 @@ -PASS selectFirstLineIncludingLineBreak(); copyPaste(); textarea.selectionEnd is offsetAfterLineBreak +FAIL selectFirstLineIncludingLineBreak(); copyPaste(); textarea.selectionEnd should be 6. Was 9.
Attachments
Miguel Gomez
Comment 1 2018-11-15 06:45:50 PST
editing/pasteboard/display-block-on-spans.html [ Failure Pass ] Same as the previous one, mostly passes but sometimes the first run fails with this diff --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/editing/pasteboard/display-block-on-spans-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/editing/pasteboard/display-block-on-spans-actual.txt @@ -20,16 +20,9 @@ " after: -| " -" -| <span> -| style="display: block;" -| <b> -| "This is a paragraph." | <span> | style="display:block" -| <b> -| "This<#selection-caret>" +| "hello, world<#selection-caret>" | <b> | " is another paragraph." | <br>
Miguel Gomez
Comment 2 2018-11-15 06:46:35 PST
Both tests were passing consistently until the first fail happened in r236540, so something around that revision caused the problem.
Diego Pino
Comment 3 2024-01-12 22:43:58 PST
The test(s) filed under this bug ticket have consistently passed for the last 4000 revisions. Currently, there are no more tests in TestExpectations that refer to this bug. Therefore, I'm closing the bug.
Note You need to log in before you can comment on or make changes to this bug.