Issue metadata
Sign in to add a comment
|
LayerTreeHostImplTest.GPUMemoryForLargeLayerHistogramTest is flaky |
||||||||||||||||||||||
Issue description
I see this test flake all the time for me on Linux.
[ RUN ] LayerTreeHostImplTest.GPUMemoryForLargeLayerHistogramTest
[9705:9705:0728/155358.705983:944182347525:WARNING:histograms.cc(40)] Started multiple compositor clients (Renderer, Browser) in one process. Some metrics will be disabled.
../../base/test/histogram_tester.cc:55: Failure
Expected: (nullptr) != (histogram), actual: 8-byte object <00-00 00-00 00-00 00-00> vs NULL
Histogram "Compositing.Browser.GPUMemoryForTilingsInKb" does not exist.
../../base/test/histogram_tester.cc:72: Failure
Expected: count
Which is: 1
To be equal to: 0
Histogram "Compositing.Browser.GPUMemoryForTilingsInKb" does not exist.
[ FAILED ] LayerTreeHostImplTest.GPUMemoryForLargeLayerHistogramTest (26 ms)
Can you look into this and make it non-flaky?
,
Jul 29 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/354a5555fef3d0f2d2e5ae999e23c0b586b12d76 commit 354a5555fef3d0f2d2e5ae999e23c0b586b12d76 Author: Adrienne Walker <enne@chromium.org> Date: Sat Jul 29 01:09:49 2017 Disable flaky GPUMemoryForLargeLayerHistogramTest Bug: 750377 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel Change-Id: I06d5fd631fc982b5eaaad521cb3d5459becb7b1e Reviewed-on: https://chromium-review.googlesource.com/592082 Reviewed-by: Khushal <khushalsagar@chromium.org> Commit-Queue: enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#490567} [modify] https://crrev.com/354a5555fef3d0f2d2e5ae999e23c0b586b12d76/cc/trees/layer_tree_host_impl_unittest.cc |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by yigu@chromium.org
, Jul 28 2017Status: Duplicate (was: Assigned)