[roll] Roll fuchsia [driver_runtime] Fix shutdown race condition.

If a channel wrote to its peer, and its peer's dispatcher was
shutting down, there was a chance the following would happen:

1) no active threads are running on the dispatcher, so it enters
   CompleteShutdown and is about to acquire the lock
2) a channel peer calls QueueRegisteredCallback on this dispatcher,
   this increments num_active_threads_ and returns
3) CompleteShutdown checks num_active_threads_ and asserts since it is
   no longer zero

Multiply: fuchsia-pkg://fuchsia.com/driver_runtime_tests#meta/driver_runtime_tests.cm : 1000

Original-Bug: 109642

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/730990
Original-Revision: 19d6e08fa91879d91924bd8b1fd03683a42157d6
GitOrigin-RevId: f5c6a5f39ffe703196bf3a660ba551b4a0fc972b
Change-Id: I99e116edd1c53d614f521824d21c200f2062d30a
1 file changed
tree: 7b8e13f49cd6a5b947f63407f3bb3f91c31b40be
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.