From: Kourt, Tim A <tim.a.kourt@linux.intel.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 1/2] auto-t: remove scanning wait from testConnectAutoconnect
Date: Wed, 06 May 2020 10:02:12 -0700 [thread overview]
Message-ID: <6790b6f3-1303-6c8a-6696-c30644f0b68f@linux.intel.com> (raw)
In-Reply-To: <CAPv5Ue65n+fHNQterpTc2GTnr9bKh_8k8OKjqd1nCuyU8h-hrg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Hi James,
>>> - 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?
> I can try increasing the timeout, but I think relying on periodic
> scans for this autotest isn't the best way to go about it. I will try
> explicitly scanning via dbus, otherwise you are just hoping that a
> periodic scan was started. This timing will vary slightly between
> systems which is why I think I am hitting this.
The purpose of this autotest and of the one with the hidden networks is
to exercise auto-connection without an explicit call from Dbus
(different code paths).
prev parent reply other threads:[~2020-05-06 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 15:58 [PATCH 1/2] auto-t: remove scanning wait from testConnectAutoconnect James Prestwood
2020-05-06 15:58 ` [PATCH 2/2] auto-t: remove scanning wait from testHiddenNetworks James Prestwood
2020-05-06 16:46 ` [PATCH 1/2] auto-t: remove scanning wait from testConnectAutoconnect Kourt, Tim A
2020-05-06 16:52 ` James Prestwood
2020-05-06 17:02 ` Kourt, Tim A [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6790b6f3-1303-6c8a-6696-c30644f0b68f@linux.intel.com \
--to=tim.a.kourt@linux.intel.com \
--cc=iwd@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox