SetupBoard failed on leon-paladin |
||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/17382 I see nothing wrong with the SetupBoard logs, it looks identical to the logs from a successful build.
,
Jan 9 2018
23:32:17: INFO: Processing relevant changes of build leon-paladin status COMPLETED result FAILURE 23:32:17: INFO: Build leon-paladin failed with not ignorable failures, will not submit changes: leon-paladin wasn't aborted by self-destruction, it stopped/failed unexpectedly, probably because the buildslave wasn't responding. I think we can live with this, as it doesn't happen very often. |
||
►
Sign in to add a comment |
||
Comment 1 by jrbarnette@chromium.org
, Jan 4 2018Status: Assigned (was: Untriaged)
My best reading: Multiple paladins were cut off by self-destruction. By all appearances, that would include leon-paladin. However, for some reason, leon-paladin didn't _report_ "aborted by self-destruction." Passing to nxia@ to address a few questions: * Did leon-paladin die because of self-destruction, or because of some other cause? * If the cause was "self-destruction", why wasn't it reported as such? * What's the next step? Do we fix it, or live with it?