Bug 191680 - [GTK] Two pasteboard tests are flaky
Summary: [GTK] Two pasteboard tests are flaky
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-15 06:43 PST by Miguel Gomez
Modified: 2018-11-15 06:46 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miguel Gomez 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.
Comment 1 Miguel Gomez 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>
Comment 2 Miguel Gomez 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.