tests: Run dump_monitor() again if scan was pending

In addition to running the FLUSH command again, the pending monitor
interface events need be cleared in case the driver was running a scan
when reset() is called. This avoids issues, e.g., with discovery_dev_id
failing due to an unexpected P2P-DEVICE-FOUND event that was generated
by the pending scan operation that had not yet complete when the first
dump_monitor() call in reset() happened.

Signed-hostap: Jouni Malinen <j@w1.fi>

diff --git a/tests/hwsim/wpasupplicant.py b/tests/hwsim/wpasupplicant.py
index 79aee26558251bfaba8a41d1d18fdf422651670f..082704b74ce47842775274dbd901b46c55abca3c 100644 (file)
--- a/tests/hwsim/wpasupplicant.py
+++ b/tests/hwsim/wpasupplicant.py
@@ -124,6 +124,7 @@ class WpaSupplicant:
             # The ongoing scan could have discovered BSSes or P2P peers
             logger.info("Run FLUSH again since scan was in progress")
             self.request("FLUSH")
+            self.dump_monitor()
 
         if not self.ping():
             logger.info("No PING response from " + self.ifname + " after reset")