Findit identified the culprit r557644 with confidence 70.0% in the config "chromium.win / Win7 Tests (dbg)(1)"
based on the flakiness trend:

https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVy4wELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKsAWNocm9taXVtLndpbi9XaW43IFRlc3RzIChkYmcpKDEpLzY4OTY4L2NjX3VuaXR0ZXN0cy9UR0Y1WlhKVWNtVmxTRzl6ZEZSbGMzUlhhV3hzUW1WbmFXNUpiWEJzUm5KaGJXVklZWE5FYVdSR2FXNXBjMmhKYlhCc1JuSmhiV1V1VW5WdVRYVnNkR2xVYUhKbFlXUmZSR1ZzWldkaGRHbHVaMUpsYm1SbGNtVnkMCxITTWFzdGVyRmxha2VBbmFseXNpcxgBDA


Automatically posted by the findit-for-me app (https://goo.gl/Ot9f7N).
Feedback is welcome! Please use component Tools>Test>FindIt>Flakiness

Sheriff triage!

pwnall@, looks like findit suspects your change (revision b88e5e3db62393f232edbcb13699c6da3fc03a04).  This seems a little unlikely to me, but mind taking a look?  If it's not yours, feel free to apply the labels described in #0.

Findit identified the culprit r560343 with confidence 70.0% in the config "chromium.win / Win7 Tests (dbg)(1)"
based on the flakiness trend:

https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVy4wELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKsAWNocm9taXVtLndpbi9XaW43IFRlc3RzIChkYmcpKDEpLzY5MTY2L2NjX3VuaXR0ZXN0cy9UR0Y1WlhKVWNtVmxTRzl6ZEZSbGMzUlhhV3hzUW1WbmFXNUpiWEJzUm5KaGJXVklZWE5FYVdSR2FXNXBjMmhKYlhCc1JuSmhiV1V1VW5WdVRYVnNkR2xVYUhKbFlXUmZSR1ZzWldkaGRHbHVaMUpsYm1SbGNtVnkMCxITTWFzdGVyRmxha2VBbmFseXNpcxgBDA


Automatically posted by the findit-for-me app (https://goo.gl/Ot9f7N).
Feedback is welcome! Please use component Tools>Test>FindIt>Flakiness

Findit identified the culprit r559895 with confidence 70.0% in the config "chromium.win / Win7 Tests (dbg)(1)"
based on the flakiness trend:

https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVy4wELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKsAWNocm9taXVtLndpbi9XaW43IFRlc3RzIChkYmcpKDEpLzY5MTY2L2NjX3VuaXR0ZXN0cy9UR0Y1WlhKVWNtVmxTRzl6ZEZSbGMzUlhhV3hzUW1WbmFXNUpiWEJzUm5KaGJXVklZWE5FYVdSR2FXNXBjMmhKYlhCc1JuSmhiV1V1VW5WdVRYVnNkR2xVYUhKbFlXUmZSR1ZzWldkaGRHbHVaMUpsYm1SbGNtVnkMCxITTWFzdGVyRmxha2VBbmFseXNpcxgCDA


Automatically posted by the findit-for-me app (https://goo.gl/Ot9f7N).
Feedback is welcome! Please use component Tools>Test>FindIt>Flakiness

As far as I can tell, cc_unittests don't depend on //content. The flake rate in #1 seems unrelated.

Detected 3 new flakes for test/step "LayerTreeHostTestWillBeginImplFrameHasDidFinishImplFrame.RunMultiThread_DelegatingRenderer". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyZQsSBUZsYWtlIlpMYXllclRyZWVIb3N0VGVzdFdpbGxCZWdpbkltcGxGcmFtZUhhc0RpZEZpbmlzaEltcGxGcmFtZS5SdW5NdWx0aVRocmVhZF9EZWxlZ2F0aW5nUmVuZGVyZXIM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Reporting to stale-flakes-reports@google.com to investigate why this issue is not being processed despite being in an appropriate queue for 7 days or more.

Detected 3 new flakes for test/step "LayerTreeHostTestWillBeginImplFrameHasDidFinishImplFrame.RunMultiThread_DelegatingRenderer". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyZQsSBUZsYWtlIlpMYXllclRyZWVIb3N0VGVzdFdpbGxCZWdpbkltcGxGcmFtZUhhc0RpZEZpbmlzaEltcGxGcmFtZS5SdW5NdWx0aVRocmVhZF9EZWxlZ2F0aW5nUmVuZGVyZXIM. This message was posted automatically by the chromium-try-flakes app.

Detected 3 new flakes for test/step "LayerTreeHostTestWillBeginImplFrameHasDidFinishImplFrame.RunMultiThread_DelegatingRenderer". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyZQsSBUZsYWtlIlpMYXllclRyZWVIb3N0VGVzdFdpbGxCZWdpbkltcGxGcmFtZUhhc0RpZEZpbmlzaEltcGxGcmFtZS5SdW5NdWx0aVRocmVhZF9EZWxlZ2F0aW5nUmVuZGVyZXIM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Detected 4 new flakes for test/step "LayerTreeHostTestWillBeginImplFrameHasDidFinishImplFrame.RunMultiThread_DelegatingRenderer". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyZQsSBUZsYWtlIlpMYXllclRyZWVIb3N0VGVzdFdpbGxCZWdpbkltcGxGcmFtZUhhc0RpZEZpbmlzaEltcGxGcmFtZS5SdW5NdWx0aVRocmVhZF9EZWxlZ2F0aW5nUmVuZGVyZXIM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

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

commit 6320189e3a90bd99894ec2eddb52d9cba99fa8c4
Author: Peter Boström <pbos@chromium.org>
Date: Mon Sep 24 20:12:28 2018

Disable flaky LayerTreeHost test

LayerTreeHostTestWillBeginImplFrameHasDidFinishImplFrame has been
reported as flaky on and off for a while now.

TBR=lijeffrey@chromium.org

Bug: chromium:842038,  chromium:845381 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ie71c4716777812d6ebec67833d98da340962b699
Reviewed-on: https://chromium-review.googlesource.com/1241193
Reviewed-by: Peter Boström <pbos@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593656}
[modify] https://crrev.com/6320189e3a90bd99894ec2eddb52d9cba99fa8c4/cc/trees/layer_tree_host_unittest.cc