aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant
diff options
context:
space:
mode:
authorJouni Malinen <jouni@qca.qualcomm.com>2016-12-09 22:33:33 (GMT)
committerJouni Malinen <j@w1.fi>2016-12-09 22:33:33 (GMT)
commita1a60635a8a94f9278e87b95b98279cb1af2c967 (patch)
treec697985b1f90e72e6cf676c3d63719b5acf34b46 /wpa_supplicant
parent49aa88bb5ea86620820553ec311e0e057b957dd2 (diff)
downloadhostap-a1a60635a8a94f9278e87b95b98279cb1af2c967.zip
hostap-a1a60635a8a94f9278e87b95b98279cb1af2c967.tar.gz
hostap-a1a60635a8a94f9278e87b95b98279cb1af2c967.tar.bz2
tests: Make p2ps_wildcard_p2ps more robust
The final check in this test case was issuing a new P2P_FIND command immediately after the P2P_SERVICE_DEL command on the peer. It looked like it was possible for the scan timing to go in a sequence that made the new P2P_FIND operation eventually accept a cfg80211 BSS entry from the very end of the previous P2P_FIND. This resulted in unexpected P2P-DEVICE-FOUND event even though there was no new Probe Response frame from the peer at that point in time. Make this less likely to show unrelated failures by waiting a bit before starting a new P2P_FIND operation after having changes peer configuration. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Diffstat (limited to 'wpa_supplicant')
0 files changed, 0 insertions, 0 deletions