New issue
Advanced search Search tips

Issue 833991 link

Starred by 0 users
Status: Available
Owner: ----
Cc:
paulmiller@chromium.org
boliu@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

No logcat info when gtest test-listing on device fails

Project Member Reported by paulmiller@chromium.org, Apr 17 2018 
See the "base_unittests" step here:
https://ci.chromium.org/buildbot/tryserver.chromium.android/linux_android_rel_ng/530223

It failed with "gtest shard timed out".

See the "result_details (logcats, flakiness links)" link under "base_unittests":
https://storage.cloud.google.com/chromium-result-details/html/base_unittests_linux_android_rel_ng_530223_2018_04_17_T00_37_17-UTC

The table is empty.

By contrast, the later "chrome_public_test_vr_apk" step as logcat error info:
https://storage.cloud.google.com/chromium-result-details/html/chrome_public_test_vr_apk_linux_android_rel_ng_530223_2018_04_17_T00_52_37-UTC

Comment 1 by bpastene@chromium.org, Apr 24 2018

Components: -Infra Infra>Client>Chrome
Labels: OS-Android
Summary: No logcat info when gtest test-listing on device fails (was: No logcat info when gtest times out)
The test timed-out in the setup phase, before we start recording logcats. Collecting the logs from more phases of a test run would certainly be helpful.

Comment 2 by bpastene@chromium.org, Apr 27 2018

Status: Available (was: Untriaged)
But unfortunately we don't have available cycles atm. Moving to our backlog.
►

Sign in to add a comment