Hi James, On 5/6/2020 8:58 AM, James Prestwood wrote: > In certain cases the test was reaching this point once already finished > with a scan. This caused the wait for 'scanning' to time out. At this point > in the test we don't need to wait for scanning and only need to wait for > scanning to finish. If scanning is already finished before validation we > can simply validate at that time. > --- > autotests/testConnectAutoconnect/validation.py | 3 --- > 1 file changed, 3 deletions(-) > > diff --git a/autotests/testConnectAutoconnect/validation.py b/autotests/testConnectAutoconnect/validation.py > index 43cbaf02..b1e3accc 100644 > --- a/autotests/testConnectAutoconnect/validation.py > +++ b/autotests/testConnectAutoconnect/validation.py > @@ -54,9 +54,6 @@ class TestConnectAutoConnect(unittest.TestCase): > self.assertIsNotNone(devices) > device = devices[0] > > - condition = 'obj.scanning' > - wd.wait_for_object_condition(device, condition) > - What if the scan has never started yet? Since iwd is started from Python, it looks suspicious that it goes through the scan before it hits the conditional wait a few lines down the script. Perhaps changing to wd.list_devices(1) API has introduced this issue. Would it help to increase the conditional wait time out so it goes into the second round of scans for these certain cases?