[roll] Roll fuchsia [scenic] Do not crash Scenic on buffer collection failure.

If a Scenic client requests to create Image2 / Image3 with a
BufferCollectionExportToken but then the client is terminated
before Scenic completes the import, sysmem will close all the
other handles to the BufferCollection and thus cause all the
buffer collection operations (including Vulkan buffer collection
API calls) to fail.

Thus we shouldn't do any debug assertion for the sysmem FIDL
call results / Vulkan call results; instead we should always
do error handling so that Scenic can tear down the Session
correctly.

Original-Bug: 93136
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/644034
Original-Revision: 061eb1937d30b07aa1fa568f843140f13cf7234c
GitOrigin-RevId: 8563ea3dc1e70a0e4d48f1245106d3c44b3225c0
Change-Id: I2e4cd8fde51143829fed151f9a75e56186180ceb
1 file changed
tree: 26d41c250456f95e3a989ec86320a397d044f9aa
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.