[roll] Roll fuchsia [sys_driver_cpp] Explicitly teardown in destructor

On ZirconConnection teardown there are a few things that need to happen
in order:
1. Disable the notification handler
2. Shutdown the loop (cancels remaining async tasks)
3. Destroy the MagmaSystemConnection (calls into the driver to tear it
   down).

Currently steps 2 and 3 are run by destructors, ordered based on their
order in the ZirconConnection. This is a bit fragile, so it's safer to
run them explicitly in the destructor.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/834938
Original-Revision: dd7ce014c2d712447ea6e7ba00b516f50bbd85e4
GitOrigin-RevId: 6c0bcd76259d28efce001348b29174f949b09d31
Change-Id: I32dc24eb434faa06c9ae9ba1bb5139307f246e37
1 file changed
tree: 78ee826aa014e2fec19ace14769abcd2a89ca38f
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.