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

Issue 689202 link

Starred by 1 user
Status: Archived
Owner:
█ sbasi@chromium.org
Last visit > 30 days ago
Closed: Aug 3
Cc:
xixuan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

M56 pfq failing AFDO test fails due to dev server timeout

Project Member Reported by gkihumba@google.com, Feb 6 2017 
M56 PFQ has been failing since 2/3. Looks like a timeout issue of AFDO tests with the dev server.

https://uberchromegw.corp.google.com/i/chromeos_release/builders/samus-pre-flight-branch%20release-R56-9000.B

server_job:0183| START	99580754-chromeos-test/chromeos2-row3-rack9-host11/provision_AutoUpdate	provision	timestamp=1486178832	localtime=Feb 03 19:27:12	
02/03 22:02:13.231 INFO |        server_job:0183| 	FAIL	99580754-chromeos-test/chromeos2-row3-rack9-host11/provision_AutoUpdate	provision	timestamp=1486187958	localtime=Feb 03 21:59:18	Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row3-rack9-host11: SSHConnectionError: Connection to 100.115.226.94 timed out while waiting to read

Link to debug log:
https://tests.corp.google.com/file?invocationId=40d565ae-9b02-4fcb-ba79-9eb8ea7c1b74&targetResultIndex=0&largeText=debug%2Fautoserv.DEBUG&filename=autoserv.DEBUG&contentType=text%2Fplain&format=ansi&setTZID=America%2FLos_Angeles

Comment 1 by sbasi@chromium.org, Feb 6 2017

Status: WontFix (was: Assigned)
Looks to be related to the lab outage last weekend:

"There will be a planned power outage for one of the labs
hosting Chrome OS test devices.  The outage will be during
the day (PST) on Saturday, 2/4.  To accomodate the outage, we
will be closing the Chrome OS test lab for the weekend.

While the lab is closed, all testing will fail:
  * Canary and release builders will be red.
  * All CQ runs will fail.
  * The Chrome PFQ will not uprev.

We anticipate that we will close the lab late Friday afternoon
2/3, and reopen by start-of-business on Monday, 2/6."


Reopen if this is still an issue tomorrow.

Comment 2 by gkihumba@google.com, Feb 8 2017

Status: Assigned (was: WontFix)

Comment 3 by gkihumba@google.com, Feb 8 2017 

Yesterday's 5pm build failed with the same error.

Comment 4 by sbasi@chromium.org, Feb 8 2017

Cc: xixuan@chromium.org
Seems to be the same DUT on each test run:
http://cautotest/afe/#tab_id=view_host&object_id=1248

Which was locked yesterday for failing continuously.
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 27 2017

Labels: Hotlist-Google

Comment 6 by dgarr...@chromium.org, Aug 3

Status: Archived (was: Assigned)
►

Sign in to add a comment