New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 599641 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 598491
Owner: ----
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

LayerTreeHostTestGpuRasterDeviceSizeChanged.RunMultiThread_DirectRenderer seen to timeout on linux_android_rel_ng

Project Member Reported by kbr@chromium.org, Mar 31 2016

Issue description

LayerTreeHostTestGpuRasterDeviceSizeChanged.RunMultiThread_DirectRenderer was seen to time out on this trybot run:

https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/45811

I can't find an entry for this test on this bot on the flakiness dashboard, and chromium-try-flakes seems to be down (Issue 599638), so not sure whether this is a pervasive problem. Checked the last 200 builds on this trybot, and don't see any cc_unittests failures.

Log excerpt:

I   22.266s run_tests_on_device(06ad9d65003bb364)  [ RUN      ] LayerTreeHostTestGpuRasterDeviceSizeChanged.RunMultiThread_DirectRenderer
I   22.266s run_tests_on_device(06ad9d65003bb364)  ../../cc/test/layer_tree_test.cc:898: Failure
I   22.266s run_tests_on_device(06ad9d65003bb364)  Failed
I   22.266s run_tests_on_device(06ad9d65003bb364)  Test timed out
I   22.266s run_tests_on_device(06ad9d65003bb364)  [  FAILED  ] LayerTreeHostTestGpuRasterDeviceSizeChanged.RunMultiThread_DirectRenderer (5011 ms)

 

Comment 1 by ajuma@chromium.org, Mar 31 2016

Cc: jaydasika@chromium.org
Mergedinto: 598491
Status: Duplicate (was: Untriaged)

Sign in to add a comment