[roll] Roll fuchsia [compat] Fix breakage with compat device release hook impl.

There was an earlier change to delay release until after the
dispatcher shutsdown, to match DFv1 behaviour:
https://fuchsia-review.git.corp.google.com/c/fuchsia/+/961879

That broke the upgrade test for
smart_display_eng.astro-release-e2e-isolated-omaha,
where a driver rebind gets stuck during paving.

To fix this, we try to match the previous passing behaviour
as much as possible - only delay the release op, but the
rest of the compat device object can destruct as normal.
The actual device's context is stored along with the release op
to be called later.

Original-Bug: 317784515

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/965633
Original-Revision: d775cf8d192640938c97bd74d2411ad6ddd34f3c
GitOrigin-RevId: 322b24f6ecd65eb33187ca179bd224a25833497a
Change-Id: Id55f5f08032c5a69a45e7e4346d81cad7d2cff2d
1 file changed
tree: 65359c17bd0a3e4daa09175e58321e428adf5378
  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.