A potential repair bug (in skylab/autotest)? |
|||
Issue descriptionchromeos15-row1-rack2-host4 is migrated to skylab and do has a servo (b/119777316). However, after a failed repair: https://chromium-swarm-dev.appspot.com/task?id=41e3124b9c862a10&refresh=10 It becomes un-pingable. Supposedly this case could be handled by servo (in my understanding), but the following repairs are all failed due to it's unpingable: https://chromium-swarm-dev.appspot.com/task?id=41e3325558b80d10&refresh=10 I don't know why it doesn't happen or I don't see it happen in cautotest.
,
Dec 20
,
Dec 21
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/1106360f1c905cf29612e3f4088665bff65b7334 commit 1106360f1c905cf29612e3f4088665bff65b7334 Author: Prathmesh Prabhu <pprabhu@chromium.org> Date: Fri Dec 21 02:06:25 2018 autotest: Also catch SSH error during host detection BUG= chromium:917080 TEST=None Change-Id: If7db695812c5048b795bdc45aeab63ded207ace5 Reviewed-on: https://chromium-review.googlesource.com/1387226 Commit-Ready: Xixuan Wu <xixuan@chromium.org> Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Xixuan Wu <xixuan@chromium.org> [modify] https://crrev.com/1106360f1c905cf29612e3f4088665bff65b7334/server/hosts/factory.py
,
Dec 26
|
|||
►
Sign in to add a comment |
|||
Comment 1 by pprabhu@chromium.org
, Dec 20Status: Started (was: Untriaged)