On Qt WK1 fast/regions/hover-on-child-parent-different-regions.html failing after r150868. --- /ramdisk/qt-linux-release/build/layout-test-results/fast/regions/hover-on-child-parent-different-regions-expected.txt +++ /ramdisk/qt-linux-release/build/layout-test-results/fast/regions/hover-on-child-parent-different-regions-actual.txt @@ -2,8 +2,8 @@ On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". -PASS Child hover event processed OK. -PASS Parent hover event processed OK. +FAIL Child hover event FAILED to process. +FAIL Parent hover event FAILED to process. PASS successfullyParsed is true TEST COMPLETE And other tests related to that revision are flaky: fast/regions/hover-on-child-in-region.html fast/regions/hover-in-region-grandparent.html fast/regions/hover-in-region-parent-skip-inlines-anonymous.html http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release/r150964%20%2851391%29/results.html It seems these test are fine on Qt WK2.
Created attachment 203562 [details] Patch Wasn't able to reproduce the problem on my Qt WK1 environment. I modified the test to overcome a possible issue with the hover check being carried out before the hover event could fire. If this patch will fix the main failing test, I will perform the same change for the other flaky tests.
Comment on attachment 203562 [details] Patch Clearing flags on attachment: 203562 Committed r151104: <http://trac.webkit.org/changeset/151104>
All reviewed patches have been landed. Closing bug.
fast/regions/hover-on-child-parent-different-regions.html unskipped in http://trac.webkit.org/changeset/151105.
Reopen, because it still fails: --- /ramdisk/qt-linux-64-release/build/layout-test-results/fast/regions/hover-on-child-parent-different-regions-expected.txt +++ /ramdisk/qt-linux-64-release/build/layout-test-results/fast/regions/hover-on-child-parent-different-regions-actual.txt @@ -1,4 +1,4 @@ -PASS Child hover event processed OK. +FAIL Child hover event FAILED to process. PASS Parent hover event processed OK.
Created attachment 203607 [details] Patch The hover event seems to be triggered only AFTER the results are checked. Forced a re-layout in an attempt to fix this.
Created attachment 203611 [details] Patch Forced relayout to ensure hover event gets called before checking the results.
Something is wrong ... fast/regions/hover-on-child-parent-different-regions.html passes for me locally, but it fails on the bot. (I haven't run all the tests, only this one and then all fast/regions tests) Additionally fast/regions/hover-in-second-region.html fails if I run all fast/regions test, but passes if I run only this one. --> expected: 7xx is red, actual: 7xx is blue It seems it needs more debugging ... but now I have to go.
Comment on attachment 203611 [details] Patch Let's see if this fixes the problem on the bots.
Comment on attachment 203611 [details] Patch Clearing flags on attachment: 203611 Committed r151121: <http://trac.webkit.org/changeset/151121>
Still flaky, fails on http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release/r151168%20%2851497%29/results.html Skipped again in http://trac.webkit.org/changeset/151171.
Probably the same issue as https://bugs.webkit.org/show_bug.cgi?id=117338 Looks like the Qt testing environment has some problems when running multiple hover tests in parallel (probably the multiple simultaneous calls to mouseMoveTo interfere with each other).
*** Bug 117338 has been marked as a duplicate of this bug. ***
I think part of the problem is that mouse-move events are not flushed in EventSenderQt.
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.