[roll] Roll fuchsia [early-boot-coverage] Make standalone-test build in instrumented variants

The coverage test binary is built with explicit switches to
enable the right instrumentation.  Don't let the usual switches
from a coverage or profile variant selection conflict.  Some
combinations are disallowed by the compiler, and others could
build fine but interfere with the instrumentation that the test
relies on (such as the selective instrumentation switches).

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/941554
Original-Revision: 41d43a07ab9a7a58c63cf027a11b11406b9b9148
GitOrigin-RevId: 16b709d86fcce1fe41eb324e39e31ae7f5cb112b
Change-Id: I9640e4dece630178d27cca014c546f39eb403788
1 file changed
tree: 92324d441034f078d6f5ebbdddc5c6e2982ae7e3
  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.