RESOLVED FIXED 88061
[Gtk] fast/replaced/border-radius-clip.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=88061
Summary [Gtk] fast/replaced/border-radius-clip.html is flaky
Zan Dobersek
Reported 2012-06-01 01:13:59 PDT
fast/replaced/border-radius-clip.html is flaky with the following diff: --- /home/slave/webkitgtk/gtk-linux-64-release/build/layout-test-results/fast/replaced/border-radius-clip-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release/build/layout-test-results/fast/replaced/border-radius-clip-actual.txt @@ -1,8 +1,8 @@ -layer at (0,0) size 785x948 +layer at (0,0) size 785x898 RenderView at (0,0) size 785x600 -layer at (0,0) size 785x924 - RenderBlock {HTML} at (0,0) size 785x924 - RenderBody {BODY} at (8,8) size 769x908 +layer at (0,0) size 785x874 + RenderBlock {HTML} at (0,0) size 785x874 + RenderBody {BODY} at (8,8) size 769x858 RenderText {#text} at (0,0) size 457x19 text run at (0,0) width 457: "All of the replaced elements below should be clipped to a border-radius. " RenderBR {BR} at (0,0) size 0x0 @@ -24,10 +24,10 @@ RenderText {#text} at (304,363) size 4x19 text run at (304,363) width 4: " " RenderBR {BR} at (0,0) size 0x0 - RenderText {#text} at (300,516) size 4x19 - text run at (300,516) width 4: " " + RenderText {#text} at (100,466) size 4x19 + text run at (100,466) width 4: " " RenderBR {BR} at (0,0) size 0x0 - RenderEmbeddedObject {EMBED} at (0,534) size 556x406 [bgcolor=#00FF00] [border: (3px solid #000000)] + RenderEmbeddedObject {EMBED} at (0,484) size 556x406 [bgcolor=#00FF00] [border: (3px solid #000000)] RenderText {#text} at (0,0) size 0x0 -layer at (8,389) size 300x150 - RenderVideo {VIDEO} at (0,381) size 300x150 +layer at (8,389) size 100x100 + RenderVideo {VIDEO} at (0,381) size 100x100 Also fails intermittently: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=fast%2Freplaced%2Fborder-radius-clip.html
Attachments
Zan Dobersek
Comment 1 2013-01-16 04:56:13 PST
The flakiness is not present anymore. Closing the bug.
Note You need to log in before you can comment on or make changes to this bug.