Bug 216650 - [WPE] Several fast/events/mouse-* tests are consistently flaky
Summary: [WPE] Several fast/events/mouse-* tests are consistently flaky
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-17 09:41 PDT by Diego Pino
Modified: 2020-09-17 09:41 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Pino 2020-09-17 09:41:19 PDT 
Unexpected flakiness: text-only failures
        fast/events/mouse-cursor-multiframecur.html [ Failure Pass ]
        fast/events/mouse-cursor.html [ Failure Pass ]
        fast/events/mouse-drag-from-frame-to-other-frame.html [ Failure Pass ]
        fast/events/mouse-drag-from-frame.html [ Failure Pass ]
        fast/events/mouse-focus-imagemap.html [ Failure Pass ]

Unexpected flakiness: timeouts
        fast/events/mouse-moved-remove-frame-crash.html [ Timeout Pass ]

The tests became flaky at range [r264103-r264117]:

r264102                       NOERROR
[r264103-r264116]             UNKNOWN
r264117                       TEXT PASS (Expected: PASS)

I cannot spot any significant change that may have affected these test, so this needs more investigation.

Diff: https://build.webkit.org/results/WPE%20Linux%2064-bit%20Release%20(Tests)/r267187%20(20056)/fast/events/mouse-cursor-multiframecur-diff.txt

--- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/fast/events/mouse-cursor-multiframecur-expected.txt
+++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/fast/events/mouse-cursor-multiframecur-actual.txt
@@ -7,10 +7,10 @@
 
 
 TEST CASE: Implicit default cursor
-Cursor Info: type=IBeam hotSpot=0,0
+Cursor Info: type=Pointer hotSpot=0,0
 
 TEST CASE: CUR file with 3 frames, largest of which (2nd frame) is 20x12 with hotspot at (18,11).
-Cursor Info: type=Custom hotSpot=18,11 image=20x12
+Cursor Info: type=Pointer hotSpot=0,0
 
 PASS successfullyParsed is true


Diff: https://build.webkit.org/results/WPE%20Linux%2064-bit%20Release%20(Tests)/r267187%20(20056)/fast/events/mouse-cursor-diff.txt

--- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/fast/events/mouse-cursor-expected.txt
+++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/fast/events/mouse-cursor-actual.txt
@@ -7,73 +7,73 @@
 
  
 TEST CASE: Implicit default cursor
-Cursor Info: type=IBeam hotSpot=0,0
+Cursor Info: type=Pointer hotSpot=0,0
 
 TEST CASE: Explicit default
 Cursor Info: type=Pointer hotSpot=0,0
 
 TEST CASE: Explicit auto
-Cursor Info: type=IBeam hotSpot=0,0
+Cursor Info: type=Pointer hotSpot=0,0
 
 TEST CASE: No cursor
-Cursor Info: type=None hotSpot=0,0
+Cursor Info: type=Pointer hotSpot=0,0
 

Diff: https://build.webkit.org/results/WPE%20Linux%2064-bit%20Release%20(Tests)/r267187%20(20056)/fast/events/mouse-drag-from-frame-to-other-frame-diff.txt

--- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/fast/events/mouse-drag-from-frame-to-other-frame-expected.txt
+++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/fast/events/mouse-drag-from-frame-to-other-frame-actual.txt
@@ -1,5 +1,3 @@
 This tests that dragging from an element that returns false from its mousedown handler will not let the subsequent mousemove events be captured by the containing frame, and allows the mouse move to get to other subframes.
   
-Drag Started
-received mousemove
-received mouseup
+


Diff: https://build.webkit.org/results/WPE%20Linux%2064-bit%20Release%20(Tests)/r267187%20(20056)/fast/events/mouse-focus-imagemap-diff.txt

--- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/fast/events/mouse-focus-imagemap-expected.txt
+++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/fast/events/mouse-focus-imagemap-actual.txt
@@ -4,7 +4,7 @@
 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
 
 
-PASS document.activeElement.id is 'focusable-area'
+FAIL document.activeElement.id should be focusable-area. Was body.
 PASS document.activeElement.id == 'focusable-area' || document.activeElement.id == 'body' is true
 PASS successfullyParsed is true