[roll] Roll fuchsia [sysmem2] better defaults when secure_required

Avoid creating an inconsistency (and constraints validation failure)
via cpu_domain_supported and/or ram_domain_supported defaults when
those fields aren't set and secure_required is set to true.

Also log usage bits when SetVerboseLogging, and try to keep the old
client name when the client name is set, as long as the length doesn't
get too excessive, for easier tracking of which Node is which.

BUG: b/306258175
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1051361
Original-Revision: bd79e282b3ed0d63f3f509ac6def8782ac4e4898
GitOrigin-RevId: 61856720082965358abb9773553a470db150e3a7
Change-Id: I45c06229f77a933f50ba1017aa779f5abbd7a716
1 file changed
tree: 983a9e4774404aad949f5158d626579da8fcfa2e
  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 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.