master-paladin restarts though the leon & daisy-spring appear to be running ok |
||||
Issue descriptionmaster paladin is restarting presumably due to leon and daisy-spring failing (see https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/14016, stage 25), but looking at both, they appear to have been interrupted themselves, see e.g. https://uberchromegw.corp.google.com/i/chromeos/builders/daisy_spring-paladin/builds/14720/steps/UnitTest/logs/stdio Is this the master cancelling them or something else going on?
,
Mar 20 2017
,
Mar 20 2017
At 12:17, we had a large number of slaves of the "chromeos" waterfall die with: https://uberchromegw.corp.google.com/i/chromeos/builders/daisy_spring-paladin/builds/14720/steps/steps/logs/stdio remoteFailed: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion. This same issue affected a large number of release builders. https://uberchromegw.corp.google.com/i/chromeos/builders/gru-release/builds/989/steps/steps/logs/stdio
,
Mar 20 2017
According to the current trooper, the Golo had a network outage at that time would could affect all waterfalls in a flaky fashion.
,
Mar 20 2017
Issue 702658 has been merged into this issue.
,
Mar 20 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by nxia@chromium.org
, Mar 20 2017It wasn't canceled by the master. Passing to current deputy to find out why it's canceled. "build": { "status": "COMPLETED", "failure_reason": "INFRA_FAILURE", "result": "FAILURE", "id": "8984582003847081488", ...