[roll] Roll fuchsia [virtualization][vsock] Run the util in its own thread

At the moment we're running the util in the main thread and the test in
a new thread which is explicitly disallowed (can't pass FIDL pointers
between threads).

This swaps to running the util in a new thread. This is a bandaid to the
larger issue of this test harness not being thread safe to unblock
some vsock work.

We'll need to re-visit allowing non-blocking commands in the future.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/717591
Original-Revision: eac1f5ea9f71136cf5e90425b6191e0ecfad8cdd
GitOrigin-RevId: 7d9116df7701220b350701507e59b7800f23cb0a
Change-Id: Ie5f2bb8f68b390b589cd378d60e051a34aec1541
1 file changed
tree: 437f5f8bb428c5192470b088cadd8ef9dcbcb638
  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.