[roll] Roll fuchsia [radar][proxy] Add connect request queue to fix startup flake

If a connect request is received immediately after radar-proxy starts,
there is a chance that it will be handled before the existing radar
devices are enumerated and a connection is established. This will cause
the connect request to be completed with an error even though radar
devices are available.

To fix this, a queue is added to hold connect requests that arrive
when there is no connection to a device. Once a connection is made, any
requests in the queue are completed using the new device.

Also re-enable radar-integration-test now that the issue is fixed.

Original-Fixed: 124621
Multiply: radar-proxy-test: 1000
Test: radar-integration-test passed on Nelson tryjobs
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/827220
Original-Revision: cecfa4a69abded19a993df2b9c40c1dbe3d8974b
GitOrigin-RevId: caccbffefcae2bdd8c16fd5d63525067582db196
Change-Id: If04b068805087f339637a3097ce9e2f23f941a2f
1 file changed
tree: 94146efed018c2be4c8b97c2b4341fdb68e5cd2b
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.