Issue metadata
Sign in to add a comment
|
afe_lock_machine.py hungs |
||||||||||||||||||||||
Issue description
/usr/local/google/crostc/toolchain-utils/afe_lock_machine.py --status --chromeos_root=. --remote=chromeos2-row9-rack8-host21.cros
hungs.
This makes our weekly chromeos source sync fail.
^CTraceback (most recent call last):
File "/usr/local/google/crostc/toolchain-utils/afe_lock_machine.py", line 661, in <module>
sys.exit(Main(sys.argv[1:]))
File "/usr/local/google/crostc/toolchain-utils/afe_lock_machine.py", line 635, in Main
machine_states = lock_manager.GetMachineStates(cmd=options.cmd)
File "/usr/local/google/crostc/toolchain-utils/afe_lock_machine.py", line 515, in GetMachineStates
host_info = self.afe.get_hosts(hostname=mod_host)
File "./src/third_party/autotest/files/server/frontend.py", line 528, in get_hosts
hosts = self.run('get_hosts', **query_args)
File "./src/third_party/autotest/files/server/cros/dynamic_suite/frontend_wrappers.py", line 131, in run
self, call, **dargs)
File "./chromite/lib/retry_util.py", line 244, in GenericRetry
return _run()
File "./chromite/lib/retry_util.py", line 171, in _Wrapper
self._retry_delay.Sleep(attempt)
File "./chromite/lib/retry_util.py", line 67, in Sleep
time.sleep(total)
KeyboardInterrupt
,
Apr 9 2018
I think the afe_lock_machine script is deprecated and not likely to be fixed any time soon (if ever); can the chromeos source sync be re-written to not use it?
,
Apr 9 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by yunlian@chromium.org
, Apr 9 2018