[roll] Roll fuchsia [tools][fuzz] Fix Connector cleanup logic

Previously a Connector would be cleaned up on any connection failure,
which was incorrect. It should only be cleaned up when it will never be
used again, i.e. when the corresponding Instance is destroyed.

To cover this behavior, another e2e test was added to match
ClusterFuzz's `test_qemu_logs_returned_on_error`.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/720243
Original-Revision: 5ffd2fc2bb023e6e0d68054e2f572217f54fcb3c
GitOrigin-RevId: 34a2f2330dbc50e34c35d1a5a7a5f6d68513e38d
Change-Id: I198e79e7f0700b1cfd8915eba9013f5c02846b6d
1 file changed
tree: dd6a826d2d79de96323f82b50fbdec4bf5f7adce
  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.