WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
173252
REGRESSION(
r217971
): [GTK] Layout Test fast/events/touch/frame-hover-update.html is failing
https://bugs.webkit.org/show_bug.cgi?id=173252
Summary
REGRESSION(r217971): [GTK] Layout Test fast/events/touch/frame-hover-update.h...
Charlie Turner
Reported
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.
Attachments
Add attachment
proposed patch, testcase, etc.
Charlie Turner
Comment 1
2017-06-12 02:52:15 PDT
And by crashing I actually meant failing!
Yusuke Suzuki
Comment 2
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?
Charlie Turner
Comment 3
2017-06-12 06:55:42 PDT
Sorry, I was trying to correct myself above, this wasn't a crash, just a failure.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug