[roll] Roll fuchsia [fx][coverage] Parsed binaryids correctly and correlate profraw files

with unstripped binaries

Because we passed the binary-correlate flag when instrumented binaries,
the generated profraw files are stripped and contained no mapping
information to generate profdata. By correctly parsing the binaryids
in the profraw files and correlate them with the unstripped binaries,
the `fx coverage` now work as expected
And also change the merging profraw files flow
from sequential to parallel.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1555780
Original-Revision: 2854fd1a02b8074f62709dd56d632f59361c7d99
GitOrigin-RevId: a02dd7c0c1963898f51ea42a52852120bfcdb6eb
Change-Id: I3a4663cdd8a546ef000b64cf3e3b5bd8cf829ecc
1 file changed
tree: 67a3ca79fa120cc801a8cf2a118ee3319daece34
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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.