158917 2016-06-19 17:22:32 -0700 [GTK] Layout test fast/scrolling/overflow-scroll-past-max.html is flaky 2021-12-30 23:42:22 -0800 1 1 1 Unclassified WebKit WebKitGTK Other PC Linux RESOLVED DUPLICATE 205159 https://bugs.webkit.org/show_bug.cgi?id=152645 P2 Normal --- 1 mcatanzaro webkit-unassigned bugs-noreply cgarcia dpino mcatanzaro simon.fraser oldest_to_newest 1203658 0 mcatanzaro 2016-06-19 17:22:32 -0700 Layout test fast/scrolling/overflow-scroll-past-max.html has been failing since it was added in r194486; it's been sometimes passing since r199375. Updating expectations. --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/fast/scrolling/overflow-scroll-past-max-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/fast/scrolling/overflow-scroll-past-max-actual.txt @@ -1 +1 @@ -PASS: scrollTop was 300 +FAIL: scrollTop was 40 1203698 1 cgarcia 2016-06-19 22:58:05 -0700 (In reply to comment #0) > Layout test fast/scrolling/overflow-scroll-past-max.html has been failing > since it was added in r194486; it's been sometimes passing since r199375. > Updating expectations. > > --- > /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/ > fast/scrolling/overflow-scroll-past-max-expected.txt > +++ > /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/ > fast/scrolling/overflow-scroll-past-max-actual.txt > @@ -1 +1 @@ > -PASS: scrollTop was 300 > +FAIL: scrollTop was 40 I think this is not a failure, it's just that we use a different scroll step on every platform. So, in GTK+ port a scroll wheel step is 40. We normally try to avoid this in tests, by just checking whether the scrollable scrolled or not, no matter how much. 1827306 2 dpino 2021-12-30 23:42:22 -0800 This test is currently crashing, both in WebKitGTK as well as WPE: Thread 1 (Thread 0x7ff923fdaf00 (LWP 75080)): #0 0x00007ff92cc2b410 in WTFCrash () at /app/webkit/WebKitBuild/Debug/lib/libWPEWebKit-1.1.so.0 #1 0x0000562309873866 in WTF::Seconds::Seconds(double) () #2 0x00005623098d13e5 in () #3 0x00005623098d1fa8 in WTR::UIScriptController::sendEventStream(OpaqueJSString*, OpaqueJSValue const*) () #4 0x000056230b6773dd in WTR::JSUIScriptController::sendEventStream(OpaqueJSContext const*, OpaqueJSValue*, OpaqueJSValue*, unsigned long, OpaqueJSValue const* const*, OpaqueJSValue const**) () #5 0x0000562309a10320 in long JSC::APICallbackFunction::callImpl<JSC::JSCallbackFunction>(JSC::JSGlobalObject*, JSC::CallFrame*) () #6 0x0000562309a0bf50 in JSC::callJSCallbackFunction(JSC::JSGlobalObject*, JSC::CallFrame*) () #7 0x00007ff8e2aff027 in () #8 0x00007fffb129af70 in () #9 0x000056230b6454df in op_call_slow_return_location () #10 0x0000000000000000 in () I'm closing this bug and reassign the test failure to https://bugs.webkit.org/show_bug.cgi?id=205159 *** This bug has been marked as a duplicate of bug 205159 ***