[roll] Roll fuchsia [memory] Don't fail if component already exited

Don't fail memory attribution if we receive a new principal request for
a principal that no longer exist. This scenario can happen if we are
slow to process incoming messages.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1249804
Original-Revision: 5136527a1ed5f07d8a1b8ad2ab2d05d7cc0087e8
GitOrigin-RevId: 08cba3c2c86bfa2549a00a1e7110967df630c531
Change-Id: I8d6b6680c87f43253bd368a852fe5be9361c3631
1 file changed
tree: e32b2cea1f21d033647a3fc54dfd3350814dc525
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 in one of the communication channels documented at get involved.

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.