The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/28fa941b63ab36876bcdc3525dfd020e94e6c0ea

commit 28fa941b63ab36876bcdc3525dfd020e94e6c0ea
Author: Reilly Grant <reillyg@chromium.org>
Date: Fri Jun 03 20:36:14 2016

Exclude failing tests on DrMemory bot.

BUG= 616837 , 617268 
TBR=oshima@chromium.org

Review URL: https://codereview.chromium.org/2032613009 .

Cr-Commit-Position: refs/heads/master@{#397795}

[modify] https://crrev.com/28fa941b63ab36876bcdc3525dfd020e94e6c0ea/tools/valgrind/gtest_exclude/cc_unittests.gtest-drmemory_win32.txt
[modify] https://crrev.com/28fa941b63ab36876bcdc3525dfd020e94e6c0ea/tools/valgrind/gtest_exclude/media_unittests.gtest-drmemory.txt

Did this start recently?

It looks like the first time this particular test failed was 2016-05-19. You can look at the history of the last 200 runs which goes back about a month:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%285%29?numbuilds=200

Hm that's well before the change to use cc::Display. The failure is us failing to do partial raster, cuz the image is flipped, so it's doing the readback at the right time, not a problem with that. But it's failing to find a texture to use in the cache maybe? Do they time out now?

Two more tests in this set have started failing with a different error:

c:\b\build\slave\drm-cr\build\src\cc\test\layer_tree_pixel_test.cc(74): error: Value of: result->HasBitmap()
  Actual: false
Expected: true

Example:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%285%29/builds/7567/steps/memory%20test%3A%20cc/logs/stdio

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/492654213effcab4f6d12cc093baed065ed11009

commit 492654213effcab4f6d12cc093baed065ed11009
Author: Reilly Grant <reillyg@chromium.org>
Date: Tue Jun 21 20:05:29 2016

Disable two more cc_unittests failing under Dr. Memory.

LayerTreeHostTilesTestPartialInvalidation.FullRaster_SingleThread_OneCopy
LayerTreeHostTilesTestPartialInvalidation.FullRaster_SingleThread_GpuRaster

BUG= 617268 
TBR=danakj@chromium.org

Review URL: https://codereview.chromium.org/2086113002 .

Cr-Commit-Position: refs/heads/master@{#401088}

[modify] https://crrev.com/492654213effcab4f6d12cc093baed065ed11009/tools/valgrind/gtest_exclude/cc_unittests.gtest-drmemory_win32.txt

 Issue 648860  has been merged into this issue.

It's not Dr. Memory specific. I'm unable to run cc_unittests locally to get consistent result.
It hangs on LayerTreePixelTest::CreateCopyOutputRequest failures (see 648860).

Nothing is ever Dr Memory specific in cc_unittests :) It just runs very loaded and exposes flake more consistently.

Flaky on Linux ASan LSan Tests

https://build.chromium.org/p/chromium.memory/builders/Linux%20ASan%20LSan%20Tests%20%281%29/builds/29745

ericrk@ would you please take a look?

I think sunnyps is making copy requests not be flaky anymore.

sunnyps@, feel free to assign back to me if this isn't related to your copy request work.

FYI: According to the flakiness trend below, it seems to begin from this build cycle https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20(dbg)(1)(32)/builds/33540

https://findit-for-me.appspot.com/waterfall/check-flake?master_name=chromium.linux&builder_name=Linux%20Tests%20(dbg)(1)(32)&build_number=33633&step_name=cc_unittests%20on%20Ubuntu-12.04&test_name=LayerTreeHostTilesTestPartialInvalidation.FullRaster_SingleThread_GpuRaster

sunnyps: can you take a look at this flake, please?

This will be addressed by my CL here: crbug.com/2609253003

I think this was always flaky - ran into some issues with my CL as well, hopefully that fix works here too.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/dc1892fc0639464d4418ccfaedfd1f95a5b947d0

commit dc1892fc0639464d4418ccfaedfd1f95a5b947d0
Author: ericrk <ericrk@chromium.org>
Date: Wed Jan 11 23:54:13 2017

Remove ForceReclaimResources

We had previously added ForceReclaimResources to BeginCommit to throttle
frame output and prevent starving the display compositor's rasterization
tasks. Unfortunately, this introduces significant overhead as well.

With the addition of the Display Scheduler, this change no longer
appears to be needed. The scheduler has independent controls for
limiting the number of pending frames, and these should be used instead
(if further tweaking is necessary).

Removing this logic does not regress the benchmarks which it was
initially added for, and seems unneeded at this point. Removing.

R=reveman@chromium.org
BUG=676852,489515, 617268 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2609253003
Cr-Commit-Position: refs/heads/master@{#443061}

[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/layers/texture_layer_unittest.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/output/compositor_frame_sink.h
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/surfaces/direct_compositor_frame_sink.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/surfaces/direct_compositor_frame_sink.h
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/surfaces/direct_compositor_frame_sink_unittest.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/surfaces/surface.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/surfaces/surface.h
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/surfaces/surface_factory.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/surfaces/surface_factory.h
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/test/layer_tree_pixel_test.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/test/layer_tree_test.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/test/test_compositor_frame_sink.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/test/test_compositor_frame_sink.h
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/trees/layer_tree_host_impl.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/trees/layer_tree_host_impl_unittest.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/trees/layer_tree_host_pixeltest_tiles.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/cc/trees/layer_tree_host_unittest.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/content/renderer/gpu/render_widget_compositor.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/content/test/layouttest_support.cc
[modify] https://crrev.com/dc1892fc0639464d4418ccfaedfd1f95a5b947d0/ui/compositor/layer_unittest.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4b443521bc4bc46b4bd1537910f089fbf1578273

commit 4b443521bc4bc46b4bd1537910f089fbf1578273
Author: ericrk <ericrk@chromium.org>
Date: Fri Jan 13 22:54:24 2017

Revert of Remove ForceReclaimResources (patchset #8 id:170001 of https://codereview.chromium.org/2609253003/ )

Reason for revert:
This has introduced flakiness into TextureLayerImplWithMailboxThreadedCallback.RunMultiThread_DelegatingRenderer, will address this and re-land.

Original issue's description:
> Remove ForceReclaimResources
>
> We had previously added ForceReclaimResources to BeginCommit to throttle
> frame output and prevent starving the display compositor's rasterization
> tasks. Unfortunately, this introduces significant overhead as well.
>
> With the addition of the Display Scheduler, this change no longer
> appears to be needed. The scheduler has independent controls for
> limiting the number of pending frames, and these should be used instead
> (if further tweaking is necessary).
>
> Removing this logic does not regress the benchmarks which it was
> initially added for, and seems unneeded at this point. Removing.
>
> R=reveman@chromium.org
> BUG=676852,489515, 617268 
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Review-Url: https://codereview.chromium.org/2609253003
> Cr-Commit-Position: refs/heads/master@{#443061}
> Committed: https://chromium.googlesource.com/chromium/src/+/dc1892fc0639464d4418ccfaedfd1f95a5b947d0

TBR=reveman@chromium.org,danakj@chromium.org,enne@chromium.org,tommi@chromium.org,brianderson@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=676852,489515, 617268 ,  681093 ,  680770 

Review-Url: https://codereview.chromium.org/2633563003
Cr-Commit-Position: refs/heads/master@{#443709}

[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/layers/texture_layer_unittest.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/output/compositor_frame_sink.h
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/surfaces/direct_compositor_frame_sink.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/surfaces/direct_compositor_frame_sink.h
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/surfaces/direct_compositor_frame_sink_unittest.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/surfaces/surface.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/surfaces/surface.h
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/surfaces/surface_factory.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/surfaces/surface_factory.h
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/test/layer_tree_pixel_test.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/test/layer_tree_test.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/test/test_compositor_frame_sink.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/test/test_compositor_frame_sink.h
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/trees/layer_tree_host_impl.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/trees/layer_tree_host_impl_unittest.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/trees/layer_tree_host_pixeltest_tiles.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/cc/trees/layer_tree_host_unittest.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/content/renderer/gpu/render_widget_compositor.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/content/test/layouttest_support.cc
[modify] https://crrev.com/4b443521bc4bc46b4bd1537910f089fbf1578273/ui/compositor/layer_unittest.cc

Changing owner to reflect who is working on this.

Marked the wrong bug on the commit, but a fix has landed here: https://codereview.chromium.org/2649043010/