Closed Hobbydos closed 1 year ago
cc @robshakir @xw-g
I see that rebootDUT already adds 10m in the waiting. If you want brutal force, maybe just add there.
I think another way (maybe better) would be continuously verifyintall, but only report failure after say (15min).
What do you think?
@xw-g I'm working on a PR for this, I'll raise it as soon as it's ready.
PR835 was merged - closing issue
Describe the bug After the rebootDUT function, there should be some mechanism to wait for the Supervisor synchronization to complete before attempting verifyInstall(). This results in the DUT returning an empty string as the OS.Version for the standby supervisor.
As a brute-force method, I simply added a
time.Sleep(5 * time.Minute)
after the reboot and the test passed successfully.To Reproduce Steps to reproduce the behavior:
""
Expected behavior Wait for the Standby Supervisor to be up and synchronized before attempting to fetch version
Additional context Once added, the test passed: