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

Issue 653753 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Oct 2017
Cc:
█ kemp@chromium.org
█ cbook@chromium.org
█ kevcheng@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

systemic hwtest timeouts in CQ run

Project Member Reported by akes...@chromium.org, Oct 7 2016 
Build: https://uberchromegw.corp.google.com/i/chromeos/builders/whirlwind-paladin/builds/5961

Job: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=79501726

This does not appear to be the same as previous whirlwind hwtest timeout. https://bugs.chromium.org/p/chromium/issues/detail?id=652545

In particular, seems like most jobs completed in a timely manner, but jetstream_DiagnosticReport timed out.

Comment 1 by akes...@chromium.org, Oct 7 2016

Summary: systemic hwtest timeouts in CQ run (was: whirlwind hwtest timed out | jetstream_DiagnosticReport timed out)
Actually, seems like this was systemic, and affected several other tests. Maybe cautotest/ or rpc server was down?

See also from the same run:https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-paladin/builds/570

Comment 2 by akes...@chromium.org, Oct 7 2016

Cc: kevcheng@chromium.org
Was cautotest/ down at this time?

Comment 3 by autumn@chromium.org, Oct 12 2016

Labels: -current-issue
Status: Unconfirmed (was: Untriaged)
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 13 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment