[roll] Roll fuchsia [usb][adb] Fix race in usb-adb-test

Currently, the test teardown logic calls the UnbindOp() on a background
thread, and then proceeds to tear down the fake root device - which
races with the background thread. If the dtor wins the race, it will
cause a failure because the UnbindOp() was called but never (not
yet) replied to. All we need to do is synchronize the UnbindOp() running
on a background thread to the testing thread via
WaitUntilUnbindReplyCalled(). This blocks TearDown() until the driver's
unbind logic actually replies to the unbind request.

Original-Bug: b/380480663
Test: fx test usb-adb-unittest
Multiply: usb-adb-test
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1162295
Original-Revision: 32478ccf0ba429e93b4212ab5bf8a0c5992e76c4
GitOrigin-RevId: dfa17c2514e936a4336773b60552e80745bc4ca9
Change-Id: I48e59e4508f314c3b5decf7f9cbb34161ad0ab90
1 file changed
tree: b41043100f0f3b082ac17a24fa1232ef720368c6
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 in one of the communication channels documented at get involved.

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.