Bug 173252 - REGRESSION(r217971): [GTK] Layout Test fast/events/touch/frame-hover-update.html is failing
Summary: REGRESSION(r217971): [GTK] Layout Test fast/events/touch/frame-hover-update.h...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Yusuke Suzuki
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-12 02:51 PDT by Charlie Turner
Modified: 2017-06-12 06:58 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charlie Turner 2017-06-12 02:51:18 PDT
The following layout test is failing on GTK

fast/events/touch/frame-hover-update.html

--- /home/charlie/git/WebKit/WebKitBuild/Debug/layout-test-results/fast/events/touch/frame-hover-update-expected.txt
+++ /home/charlie/git/WebKit/WebKitBuild/Debug/layout-test-results/fast/events/touch/frame-hover-update-actual.txt
@@ -6,15 +6,15 @@
 PASS hoveredTop.length is 1
 PASS hoveredIframe1.length is 0
 PASS hoveredIframe2.length is 1
-PASS hoveredTop.length is 0
+FAIL hoveredTop.length should be 0. Was 1.
 PASS hoveredIframe1.length is 0
-PASS hoveredIframe2.length is 0
+FAIL hoveredIframe2.length should be 0. Was 1.
 PASS hoveredTop.length is 1
 PASS hoveredIframe1.length is 0
-PASS hoveredIframe2.length is 0
+FAIL hoveredIframe2.length should be 0. Was 1.
 PASS hoveredTop.length is 1
 PASS hoveredIframe1.length is 0
-PASS hoveredIframe2.length is 0
+FAIL hoveredIframe2.length should be 0. Was 1.
 PASS successfullyParsed is true
 
 TEST COMPLETE

Probable cause:

Unknown, it appears to have started crashing in one of r217970,  r217971 or r217972

It seems like r217971 is most likely, as r217970 was specific to WPE, and r217972 doesn't seem like it could have caused such a regression. But I'm not sure.
Comment 1 Charlie Turner 2017-06-12 02:52:15 PDT
And by crashing I actually meant failing!
Comment 2 Yusuke Suzuki 2017-06-12 06:32:14 PDT
(In reply to Charlie Turner from comment #1)
> And by crashing I actually meant failing!

Can we have a backtrace for the crash?
Comment 3 Charlie Turner 2017-06-12 06:55:42 PDT
Sorry, I was trying to correct myself above, this wasn't a crash, just a failure.