[roll] Roll fuchsia [loadbench] Reset trace buffer before running unittests

The loadbench unittests sometimes invoke zx_ktrace_read and verify
that the resulting trace data can be successfully parse.
This generally works, but can fail in the following scenario:
1. A prior test starts tracing, which causes all of the metadata to
   be emitted.
2. The previous test consumes some of this trace data.
3. The previous test stops tracing, but does not clear out all of
   the trace buffer contents.
4. This test then reads the contents of the trace buffer, which lacks
   some of the metadata needed to parse the contents.

This only shows up when streaming data because that's the only way
a previous test could possibly consume the metadata. In saturating
mode, the ktrace implementation ensures that metadata is emitted
before reading.

Original-Bug: 404539312
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1275677
Original-Revision: 57409c89c22ac68bf790f13ca90b58a81b5bd740
GitOrigin-RevId: 0cbf6598ef6deed32af61f51ff65242fdbfde1d0
Change-Id: I21886dc0eafbd83485bc2256df27212ab3ddc0b8
1 file changed
tree: 32569d1696230337f9362910b97efe9eeab123ca
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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.