[roll] Roll fuchsia [bazel][driver] Make Bazel built drivers track the inputs correctly

In this CL I listed all the inputs needed by the underlying Bazel driver target as inputs and pass it down to the bazel_action. I tested locally and the `fx build` is working correctly now, but somehow the `fx test` is still not rebuilt automatically with change.

While I'm looking at the `fx test` issue, you can do a `fx build && fx test ...` to unblock you for now.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1048372
Original-Revision: b8549ce238970871402ad940e43f1c21f9ab55a2
GitOrigin-RevId: aaaeffd0c3caac2422db786b10b27050a18744d3
Change-Id: I7eeb212a49e09a8aa71ce9d9706cb0bb8f4b9f22
1 file changed
tree: a3da8c37b9759f141bcef82c7a25081bde8956a3
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.