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

Issue 647489 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Paladin builders failing HWTest: "urlopen error [Errno 111] Connection refused"

Reported by jrbarnette@chromium.org, Sep 15 2016

Issue description

A number of CQ runs have failed in a distinct, apparently new
fashion.  Here's the most egregious example:
    https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/12355

Something around 8 of the paladins in that run failed with
the symptom.  The failure signature is this report in the HWTest
logs:
  <class 'urllib2.URLError'>(<urlopen error [Errno 110] Connection timed out>)

Different builders report different tracebacks.  In all
cases, the evidence is that the ultimate failure is that an
RPC call to cautotest was rejected with ECONNREFUSED.

 
Cc: sbasi@chromium.org
Owner: shuqianz@chromium.org
Passing on to this week's deputy.  I don't know if this
has happened since I saw it last.  If it's not recurring,
I reckon we can close it.

Status: WontFix (was: Available)
Feel free to reopen it if it happens again

Sign in to add a comment