[roll] Roll infra/recipes [coverage] Modify coverage recipe to correctly collect coverage in

internal builders

After fixing the covargs bug of merging profile files (fxr/1571176), we
need to modify recipe to provide build-id-dir in internal coverage
builders.

By extracting binaryIds for all the profraw files entries in
summary.json files, we can then downloaded unstripped binaries from gcs
internal artifacts bucket, and save into a `.build-id` directory, finanlly
pass this directory into covargs enable us to correctly merge profile
files.
The process of public coverage builder remains the same, we will skip
the whole extracting and downloading process in public builder.

And since we moved the step:"create tree of covargs inputs" earlier in
the recipe to let the builder see the summary.json files, we also need
to update the golden files for recipe tests.

Original-Bug: 493060950

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1574517
Original-Revision: 5ca6ab351e30cf68c2f2e8dd8de90cd1b195a67a
GitOrigin-RevId: 00379bacaf16df1a5deef327626d825bb3f7bfc9
Change-Id: I1737bb959ce49730ebcf0e58fb68778ea31ce65d
1 file changed
tree: 4f1e3898849fbf9ae5d83ca1746e98beae0317c5
  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.