[roll] Roll fuchsia [test_manager] Creates a specific type of test for starnix

The starnix test currently run a linux binary with a starnix runner
outside of the test realm.

This is problematic for 2 reasons:
- The test is not hermetic at all.
- There is no code coverage on the runner code

To fix this, the runner will instead be run inside the realm of the
test.

The runner requires a number of permission that we do not want to give
to every test. To allow only giving these permissions to the test that
needs it, this CL introduce a specific type of tests and a specific
collection to run these tests in.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/682964
Original-Revision: 43a6feb05c66bfd50f2184ba0a529cbac26deb19
GitOrigin-RevId: 2d68edfb18632605cf06a2fabfed2e34bd93c228
Change-Id: I5dc2a224569ae8b7f8c6fc503a14e69d3868bc6d
1 file changed
tree: a2aa0fd85cd94bc30d3c895ff81327f644064bf7
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.