[roll] Roll fuchsia [wlan][policy] Retry with new sme_proxy

If policy receives a ShouldWait or CanceledByDriverOrFirmware error from
SME, the scan is retried one second later without ever sending an error
to the requester. However, we currently re-use the same sme_proxy, which
was resulting in the retry failing immediately.

This change restructures the scan logic to create a new sme_proxy for
the retry. This required moving where the retry actually happens,
because the sme_scan function does not have access to iface_manager to
create an sme_proxy.

Original-Bug: 102144
Test: Re-wrote retry test to match new behavior.
Multiply: wlancfg-tests

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/692392
Original-Revision: 18ada297aaaf92662d4d017f1479c47f103a8adb
GitOrigin-RevId: e66673db259ed266477201bb23a396192295b35b
Change-Id: I8f338677d68b0e166f3d37aa8443d397191c0e8a
1 file changed
tree: 231aa5bbb8e94227d282a818784362fbd4177921
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.