Surface Synchronization: Disable CompositorImplLowEndBrowserTest test

This test is no longer valid once surface synchronization is on.

Bug: 855533
Change-Id: If8feae783911501b7962183b367b0c69d8371e62
Reviewed-on: https://chromium-review.googlesource.com/1141110
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575835}

content/browser/renderer_host/compositor_impl_android_browsertest.cc

@@ -180,6 +180,13 @@ class CompositorFrameRunLoop : public ui::WindowAndroidObserver {
 
 IN_PROC_BROWSER_TEST_P(CompositorImplLowEndBrowserTest,
                        CompositorImplDropsResourcesOnBackground) {
+  // This test makes invalid assumptions when surface synchronization is
+  // enabled. The compositor lock is obsolete, and inspecting frames
+  // from the CompositorImpl does not guarantee renderer CompositorFrames
+  // are ready.
+  if (features::IsSurfaceSynchronizationEnabled())
+    return;
+
   auto* rwhva = render_widget_host_view_android();
   auto* compositor = compositor_impl();
   auto context = GpuBrowsertestCreateContext(

testing/buildbot/filters/viz.android.content_browsertests.filter

 # Android Failures
 
-# GL initiazation failures. https://crbug.com/855554
--P/CompositorImplLowEndBrowserTest.CompositorImplDropsResourcesOnBackground/0
-
 # Flaky failures with incorrect Input event acks. https://crbug.com/855532
 -TouchInputBrowserTest.TouchHandlerConsume
 -TouchInputBrowserTest.TouchHandlerNoConsume
@@ -21,4 +18,4 @@
 -SitePerProcessHitTestBrowserTest.CrossProcessMouseCapture*
 
 # /2 Variant does not handle overlapping surfaces: https://crbug.com/846798
--SitePerProcessHitTestBrowserTest.HitTestStaleDataDeletedView*
\ No newline at end of file
+-SitePerProcessHitTestBrowserTest.HitTestStaleDataDeletedView*