[roll] Roll fuchsia [vfs] Fix bad tests that fail with upcoming change.

The test helpers were joining with a server future, but the server
future would never complete so I can't see how the joined future would
ever complete. What matters is whether the client future completes, so
restructure so we just check that. A potential upcoming change exposed
this. The fix here means the tests pass both before and after the
upcoming change.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/458268
Original-Revision: 3716f12ac41ec4fd92fa50a665284ee9d8a3f5ea
GitOrigin-RevId: 43c2be7723f3bb5b6d14e1c3e130dbb2b5250eea
Change-Id: I0feb2151cf6f69d40eaf8a28c8fc4241d9659757
1 file changed
tree: 62fa0035cc69c39d3a4cdfcb557df1bea66dad6d
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. flower
  8. jiri.lock
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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 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.