chromeos2-row7-rack8-host17 (elm, pool:suites) keeps failing with "AC power is not plugged" |
||||||||
Issue descriptionLooking at recent test, many provision/repair/reset jobs on chromeos2-row7-rack8-host17 (pool:suites) fail with this kind of error: 09/24 11:36:46.478 ERROR| repair:0332| Failed: The DUT is plugged in to AC power Traceback (most recent call last): File "/usr/local/autotest/client/common_lib/hosts/repair.py", line 329, in _verify_host self.verify(host) File "/usr/local/autotest/server/hosts/cros_repair.py", line 90, in verify 'AC power is not plugged in') AutoservVerifyError: AC power is not plugged in https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos2-row7-rack8-host17/1281534-provision/20172409112648/debug/ https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos2-row7-rack8-host17/1280796-reset/20172409084022/debug/ https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos2-row7-rack8-host17/1280694-reset/20172409082350/debug/ etc.. Eventually, the host ends up passing the repair job, so it keeps failing random jobs.
,
Feb 13 2018
Hi, Sheriff here. This DUT (chromeos2-row7-rack8-host17) has been locked since 2017-09-24 17:44:29. Do we want to just keep the dut locked?
,
Feb 14 2018
We could try unlocking it and see if the issue fixed itself, but that seems unlikely... (if you do so, please monitor the device for random failed tests) Ideally we should try to dig a bit deeper, to understand why this is happening, and possibly physically inspect/replace the device.
,
May 17 2018
,
May 21 2018
,
May 21 2018
drinkcat@, can we physically inspect the device to see what is the issue?
,
May 21 2018
Sure, we should inspect it. I'm based in TPE, so doing it myself entails taking a long flight... I'd prefer if somebody in MTV could do it. Thanks!
,
May 29 2018
filed bug b/80425634
,
May 29 2018
It is fixed by the lab team
,
May 31 2018
Looks better now, device has been running quite a number of tests without showing the issue in #0. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by drinkcat@chromium.org
, Sep 25 2017