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

Issue 775294 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: May 2018
Cc:
█ nxia@chromium.org
pprabhu@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

stumpy-paladin: Suite timed out due to slow provision

Project Member Reported by nxia@chromium.org, Oct 17 2017 
https://luci-milo.appspot.com/buildbot/chromeos/stumpy-paladin/29965

Found error log:

"10/15 23:43:31.502 ERROR|                db:0023| 23:43:31 10/15/17: An operational error occurred during a database operation: (2006, 'MySQL server has gone away'); retrying, don't panic yet"

Was the abort caused by the db connection error?

Comment 1 by pprabhu@chromium.org, Oct 19 2017 

The mysql error says, and is, benign. (It says don't panic yet).

The problem is that one of the tests platform_ToolchainOptions hadn't finished by the time suite job timed out: https://viceroy.corp.google.com/chromeos/suite_details?job_id=149261987


The root cause seems to be very slow provision. This points at devserver or that particular shard slowness.

Comment 2 by pprabhu@chromium.org, Oct 19 2017

Summary: stumpy-paladin: Suite timed out due to slow provision (was: stumpy-paladin: Suite job was aborted)

Comment 3 by ayatane@chromium.org, May 11 2018

Status: Archived (was: Untriaged)
►

Sign in to add a comment