Paladin failed to connect to MySQL instance
Reported by
vpalatin@chromium.org,
Sep 20 2016
|
||||||
Issue descriptionThe elm-paladin just failed its HWtest stage because it did not manage to connect to the MySQL server. OperationalError: (2013, "Lost connection to MySQL server at 'reading initial communication packet', system error: 0") https://uberchromegw.corp.google.com/i/chromeos/builders/elm-paladin/builds/627/steps/HWTest%20%5Bbvt-inline%5D/logs/stdio despite retrying for 1 hour
,
Sep 20 2016
Other jobs are failing on the MySQL issue: https://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-chrome-pfq/builds/9134/steps/HWTest%20%5Bsanity%5D/logs/stdio
,
Sep 20 2016
,
Sep 20 2016
Lost connection to MySQL server at 'reading initial communication packet', system error: 0" That failure is from TKO database (CloudSQL instance storing results). I was doing some cleanup and have to restart the instance at one point. The instance went back online around 12, it should be all working now.
,
Sep 20 2016
,
Sep 20 2016
This affected all of the *-chrome-pfq builders in the last completed run: https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/3389
,
Sep 21 2016
Per #4, this was a transient failure. elm-paladin shows green for builds > 628->633. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by vpalatin@chromium.org
, Sep 20 2016