Bug 76385 - [GTK] tables/mozilla_expected_failures/marvin/table_overflow_dirty_reflow_tbody.html is flaky
Summary: [GTK] tables/mozilla_expected_failures/marvin/table_overflow_dirty_reflow_tbo...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Philippe Normand
URL:
Keywords: Gtk, LayoutTestFailure
Depends on:
Blocks:
 
Reported: 2012-01-16 08:47 PST by Philippe Normand
Modified: 2020-11-04 08:28 PST (History)
3 users (show)

See Also:


Attachments
Patch (1.56 KB, patch)
2012-01-16 09:00 PST, Philippe Normand
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Normand 2012-01-16 08:47:35 PST
on 32-bit Release only though. Diff:

--- /var/lib/buildbot/build/gtk-linux-32-release/build/layout-test-results/tables/mozilla_expected_failures/marvin/table_overflow_dirty_reflow_tbody-expected.txt 
+++ /var/lib/buildbot/build/gtk-linux-32-release/build/layout-test-results/tables/mozilla_expected_failures/marvin/table_overflow_dirty_reflow_tbody-actual.txt 
@@ -1,31 +1,18 @@
-layer at (0,0) size 784x728
+layer at (0,0) size 784x612
   RenderView at (0,0) size 784x600
-layer at (0,0) size 784x532
-  RenderBlock {HTML} at (0,0) size 784x532
-    RenderBody {BODY} at (8,8) size 768x516
-      RenderTable {TABLE} at (0,0) size 230x516 [border: (1px outset #808080)]
+layer at (0,0) size 784x416
+  RenderBlock {HTML} at (0,0) size 784x416
+    RenderBody {BODY} at (8,8) size 768x400
+      RenderTable {TABLE} at (0,0) size 230x400 [border: (1px outset #808080)]
         RenderBlock {CAPTION} at (0,0) size 230x206 [border: (3px solid #FFA500)]
           RenderText {#text} at (103,3) size 24x17
             text run at (103,3) width 24: "cap"
-        RenderTableSection {TBODY} at (1,207) size 228x308
-          RenderTableRow {TR} at (0,30) size 228x86
-            RenderTableCell {TD} at (30,48) size 54x50 [border: (1px inset #808080)] [r=0 c=0 rs=1 cs=1]
+        RenderTableSection {TBODY} at (1,207) size 228x192
+          RenderTableRow {TR} at (0,30) size 228x132
+            RenderTableCell {TD} at (30,71) size 54x50 [border: (1px inset #808080)] [r=0 c=0 rs=1 cs=1]
               RenderText {#text} at (16,16) size 22x17
                 text run at (16,16) width 22: "foo"
-            RenderTableCell {TD} at (114,30) size 84x86 [border: (1px inset #808080)] [r=0 c=1 rs=1 cs=1]
-              RenderText {#text} at (16,16) size 21x17
-                text run at (16,16) width 21: "bar"
-              RenderBR {BR} at (36,16) size 1x17
-              RenderText {#text} at (16,34) size 23x17
-                text run at (16,34) width 23: "baz"
-              RenderBR {BR} at (38,34) size 1x17
-              RenderText {#text} at (16,52) size 23x17
-                text run at (16,52) width 23: "zap"
-          RenderTableRow {TR} at (0,146) size 228x132
-            RenderTableCell {TD} at (30,187) size 54x50 [border: (1px inset #808080)] [r=1 c=0 rs=1 cs=1]
-              RenderText {#text} at (16,16) size 22x17
-                text run at (16,16) width 22: "foo"
-            RenderTableCell {TD} at (114,194) size 84x84 [border: (1px inset #808080)] [r=1 c=1 rs=1 cs=1]
+            RenderTableCell {TD} at (114,78) size 84x84 [border: (1px inset #808080)] [r=0 c=1 rs=1 cs=1]
               RenderBlock {DIV} at (16,16) size 52x52 [border: (1px solid #008000)]
                 RenderBlock {DIV} at (1,1) size 402x302 [border: (1px solid #FF0000)]
                   RenderText {#text} at (1,1) size 8x17
Comment 1 Philippe Normand 2012-01-16 08:48:30 PST
Err 64-bit Debug too.
Comment 2 Philippe Normand 2012-01-16 08:55:30 PST
I suspect this:

<body  onload="window.setTimeout('domfunc()',10)">

Could be the layout of the table takes more than 10ms in some cases, introducing flakiness. Will increase it to 100ms.
Comment 3 Philippe Normand 2012-01-16 09:00:17 PST
Created attachment 122647 [details]
Patch
Comment 4 Philippe Normand 2012-01-16 09:01:06 PST
(In reply to comment #3)
> Created an attachment (id=122647) [details]
> Patch

I checked this fix locally, out of 50 iterations of the test no flakiness!
Comment 5 Philippe Normand 2012-01-23 00:43:33 PST
(In reply to comment #4)
> (In reply to comment #3)
> > Created an attachment (id=122647) [details] [details]
> > Patch
> 
> I checked this fix locally, out of 50 iterations of the test no flakiness!

I'll mark the test flaky in the expectations but it'd be great to get this patch reviewed. From what Martin told me, he's not sure how to review patches modifying imported tests.
Comment 6 Julien Chaffraix 2012-01-24 17:53:13 PST
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > Created an attachment (id=122647) [details] [details] [details]
> > > Patch
> > 
> > I checked this fix locally, out of 50 iterations of the test no flakiness!
> 
> I'll mark the test flaky in the expectations but it'd be great to get this patch reviewed. From what Martin told me, he's not sure how to review patches modifying imported tests.

Usually we prefer to point out the issue upstream, have it fixed and merge a newer version of the test or test suite.

Here I am not really sure bumping the time taken to run the test is the way to go (especially to such a high value). If the problem is a partial layout, then it sounds like you should force layout at the appropriate time, not hope that WebKit will be done by your new deadline (unless I am missing something).
Comment 7 Philippe Normand 2012-04-19 15:55:50 PDT
Comment on attachment 122647 [details]
Patch

Removing r flag. It seems indeed that updating the test like this is not a great option in this case.
Comment 8 Diego Pino 2020-11-04 08:28:18 PST
This test(s) has been consistenly failing for the last 4000 revisions, that means the test(s) is no flaky anymore. The test(s) has been gardened and its baseline updated in r269363. Closing bug.