[roll] Roll fuchsia [trace] Manage rust trace contexts via RAII wrapper

Some specialized trace producers may want to be able to avoid the
computation to compute trace arguments, events, etc when tracing is not
enabled. For this purpose, it is more natural to try acquiring a
context and use that context to write the record after said computation,
rather than first checking if tracing is enabled for the category and
then later obtaining the context which would result in a second check
(and may also give a different result from the first check).

Original-Bug: b/271467732

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/869159
Original-Revision: 9721cce5cb8ca87e5ea468e21e7e82970415ae5c
GitOrigin-RevId: d83f6d669f5c2213570324d0d82595cf54210a08
Change-Id: I3eea00c7a6537addccd7955dadb58b2c424ba195
1 file changed
tree: bb7b63b10b584e001d93a1986ac4aeed0f925cc8
  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.