From 65831df17eec7857fdacc77934ba8babcd308baa Mon Sep 17 00:00:00 2001 From: Steven Koo Date: Thu, 2 Sep 2021 11:20:09 -0500 Subject: ci: Device wait to redlock scope for Vivado close Sometimes Vivado gets reopened too fast causing port in use errors. This moves the device reboot wait into the redlock scope to give some time for Vivado to close before the next agent tries to get the lock. Signed-off-by: Steven Koo --- .ci/utils/mutex_hardware.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to '.ci') diff --git a/.ci/utils/mutex_hardware.py b/.ci/utils/mutex_hardware.py index 563ec5b1a..5e16c86fb 100644 --- a/.ci/utils/mutex_hardware.py +++ b/.ci/utils/mutex_hardware.py @@ -36,8 +36,8 @@ def jtag_x3xx(jtag_args, redis_server): jtag_host.run(vivado_program_jtag + " " + os.path.join(remote_working_dir, os.path.basename(fpga_path)) + " " + jtag_serial) - print("Waiting 15 seconds for device to come back up", flush=True) - time.sleep(15) + print("Waiting 15 seconds for device to come back up and for Vivado to close", flush=True) + time.sleep(15) def main(args): -- cgit v1.2.3