[roll] Roll fuchsia [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
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1446055
Original-Revision: 6b03516a5e18cc6a681adef2d627b7c565d99060
GitOrigin-RevId: c50f224945b3337e56dee0094132da7d5bee75b4
Change-Id: I119ea54f9cafd0319ac6c3fecfd691b0f3b07468
1 file changed
tree: e340a4a9886b4700fa0f258019636e5c1b5beffe
  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.