tests: Wait before initiating DPP from thread in sigma_dut testing
Starting a thread to initiate DPP before starting the responder through sigma_dut can result in unexpected testing behavior since there may not be enough time to get the responder enabled before timing out som initiator actions. Wait a second at the beginning of the initiator thread in dpp_init_conf() similarly to how this was handled in other initiator-from-thread cases. Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
cefd959566
commit
004f618613
1 changed files with 1 additions and 0 deletions
|
@ -2726,6 +2726,7 @@ def run_sigma_dut_dpp_pkex_responder(dev, apdev, v1=False):
|
||||||
stop_sigma_dut(sigma)
|
stop_sigma_dut(sigma)
|
||||||
|
|
||||||
def dpp_init_conf(dev, id1, conf, conf_id, extra):
|
def dpp_init_conf(dev, id1, conf, conf_id, extra):
|
||||||
|
time.sleep(1)
|
||||||
logger.info("Starting DPP initiator/configurator in a thread")
|
logger.info("Starting DPP initiator/configurator in a thread")
|
||||||
cmd = "DPP_AUTH_INIT peer=%d conf=%s %s configurator=%d" % (id1, conf, extra, conf_id)
|
cmd = "DPP_AUTH_INIT peer=%d conf=%s %s configurator=%d" % (id1, conf, extra, conf_id)
|
||||||
if "OK" not in dev.request(cmd):
|
if "OK" not in dev.request(cmd):
|
||||||
|
|
Loading…
Reference in a new issue