[roll] Roll fuchsia [driver_manager] Specify collection name to runner directly

Because package name is not the only consideration when choosing which
collection to place the driver, we shouldn't rely on using the package
type to determine the collection name in the runner code. This was
missed by the last attempt to remedy this.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/857977
Original-Revision: ed67892747aedbfab40333998d393e3dc95df444
GitOrigin-RevId: c0d3710b478c9bc9ed13f3a17f36b5b6407cd330
Change-Id: Ia4431c080d0691d320504216b2318a019b395d45
1 file changed
tree: 97e40249723f6387c6fcd9bb4a72aac091458512
  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.