Bug 192432 – [GTK] compositing/backing/backing-store-attachment-scroll.html is failing

• Status: NEW
• Component: WebKitGTK

[Alicia Boya García]

compositing/backing/backing-store-attachment-scroll.html

Failing on GTK since r238487-238613

         (GraphicsLayer
           (position 8.00 2608.00)
           (bounds 300.00 300.00)
           (drawsContent 1)
-          (backingStoreAttached 0)
+          (backingStoreAttached 1)
         )

[Alicia Boya García]

From the same test run:

compositing/tiling/tile-coverage-on-scroll.html

--- /home/slave/webkitgtk/gtk-linux-64-debug-tests/build/layout-test-results/compositing/tiling/tile-coverage-on-scroll-expected.txt
+++ /home/slave/webkitgtk/gtk-linux-64-debug-tests/build/layout-test-results/compositing/tiling/tile-coverage-on-scroll-actual.txt
@@ -6,21 +6,12 @@
     (GraphicsLayer
       (bounds 785.00 5016.00)
       (contentsOpaque 1)
-      (tile cache coverage 0, 0 785 x 1024)
-      (tile size 785 x 512)
-      (top left tile 0, 0 tiles grid 1 x 2)
-      (in window 1)
       (children 1
         (GraphicsLayer
           (position 8.00 8.00)
           (bounds 100.00 5000.00)
-          (usingTiledLayer 1)
           (contentsOpaque 1)
           (drawsContent 1)
-          (tile cache coverage 0, 0 100 x 1024)
-          (tile size 512 x 512)
-          (top left tile 0, 0 tiles grid 1 x 2)
-          (in window 1)
         )
       )
     )
@@ -36,21 +27,12 @@
     (GraphicsLayer
       (bounds 785.00 5016.00)
       (contentsOpaque 1)
-      (tile cache coverage 0, 2560 785 x 1536)
-      (tile size 785 x 512)
-      (top left tile 0, 5 tiles grid 1 x 3)
-      (in window 1)
       (children 1
         (GraphicsLayer
           (position 8.00 8.00)
           (bounds 100.00 5000.00)
-          (usingTiledLayer 1)
           (contentsOpaque 1)
           (drawsContent 1)
-          (tile cache coverage 0, 2560 100 x 1536)
-          (tile size 512 x 512)
-          (top left tile 0, 5 tiles grid 1 x 3)
-          (in window 1)
         )
       )
     )

[Miguel Gomez]

This is now crashing, as reported in bug 200534. I'm adding the crash expectation, so when that's fixed we don't lose info about this fail.