[roll] Roll fuchsia Reland "[driver_runtime] Spawn up to 1 thread for non-sync-call dispatchers"

This is a reland of commit 6b03516a5e18cc6a681adef2d627b7c565d99060

Relanding with the flaking test disabled while I fix it. The test is
just flaking because the number of threads being spawned has changed
and it is sensitive to the thread count, but I want to unblock the
overall fix while I work on the test.

Original change's description:
> [driver_runtime] Spawn up to 1 thread for non-sync-call dispatchers
>
> We should still pro-actively try to spawn a thread if a non-sync-
> call dispatcher is created. This happens fairly rarely still so it
> doesn't really negatively impact the total thread count to do so
> but it will make it less likely to have stalls affect things.
>
> Original-Fixed: 467410367
> Change-Id: I604f27aeac62b3d677f6a89e4b6e8d6b3a04177f
> Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1446055
> Commit-Queue: Megan Batty <mgnb@google.com>
> Reviewed-by: Nick Eaton <nickeaton@google.com>
> Fuchsia-Auto-Submit: Megan Batty <mgnb@google.com>
> Reviewed-by: Suraj Malhotra <surajmalhotra@google.com>

Original-Fixed: 467410367
Multiply: driver_runtime_tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1449009
Original-Revision: 685b3cd516fc61bef7fd3153d49cdf05a290a45c
GitOrigin-RevId: 76ea25f88df7361a788dc6a1775c72a613e197ff
Change-Id: I880145225bed185f9adf77bc4b7015ab6bff8981
1 file changed
tree: 67d9429b2cb55e9d8de3c2e2ebc3b5dc9c92fdf6
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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.