HWTest did not complete due to infrastructure issues (code 3) |
|||
Issue descriptionI observe a few canary builders fail at HWTest with the same infra complaints: TestLabFailure: ** HWTest did not complete due to infrastructure issues (code 3) ** Examples: https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Feve-release%2F1593%2F%2B%2Frecipes%2Fsteps%2FHWTest__bvt-inline_%2F0%2Fstdout https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Fceles-release%2F2179%2F%2B%2Frecipes%2Fsteps%2FHWTest__sanity_%2F0%2Fstdout https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Fhana-release%2F1717%2F%2B%2Frecipes%2Fsteps%2FHWTest__bvt-arc_%2F0%2Fstdout
,
May 7 2018
First one, the suite timed out. Second one, looks like TKO issue that caused failure to get final results. Third one, suite timeout. Let deputy own this for now
,
May 7 2018
see error "05/07 07:25:59.832 ERROR| db:0023| 07:25:59 05/07/18: An operational error occurred during a database operation: (2006, 'MySQL server has gone away'); retrying, don't panic yet" on the timeout suites.
,
May 10 2018
it could be caused by the TKO connection flake. we have updated the TKO IP to the external primary to avoid the flake in proxy. haven't seen the issue the recent two eve-release. archiving the bug. |
|||
►
Sign in to add a comment |
|||
Comment 1 by philipchen@chromium.org
, May 7 2018