James Prestwood 14df50a0ab auto-t: fix random failures in testEAP-MSCHAPV2 ... Its difficult to know 100%, but this random test failures appeared to be caused by two issues. One was that get_ordered_network is being checked for None, when it was returning a zero length array. Because of this the scanning block was never executed in any cases. This was fixed in the previous commit. The other issue was the disconnect at the start of the tests. The disconnect will cause all pending scans to cancel, which appeared to cause the scanning block below to be skipped over quickly if the timing was right. Then, afterwards, getting a single network failed because scanning was not complete.		2019-10-28 15:01:33 -05:00
..
connection_test.py	auto-t: fix random failures in testEAP-MSCHAPV2	2019-10-28 15:01:33 -05:00
hw.conf	autotests: add autotest for eap-mschapv2	2016-12-14 23:01:00 -06:00
ssidEAP-MSCHAPV2-1.8021x	autotests: Test 4 ways MsCHAPv2 can be configured	2018-06-13 12:18:08 -05:00
ssidEAP-MSCHAPV2-2.8021x	autotests: Test 4 ways MsCHAPv2 can be configured	2018-06-13 12:18:08 -05:00
ssidEAP-MSCHAPV2-3.8021x	autotests: Test 4 ways MsCHAPv2 can be configured	2018-06-13 12:18:08 -05:00
ssidEAP-MSCHAPV2-4.8021x	autotests: Test 4 ways MsCHAPv2 can be configured	2018-06-13 12:18:08 -05:00
ssidEAP-MSCHAPV2.conf	autotests: Test 4 ways MsCHAPv2 can be configured	2018-06-13 12:18:08 -05:00