[roll] Roll fuchsia [build] Fix toolchain redirect

This group is intended to redirect test packages targets included in a
non-default toolchain to the corresponding target in the default
toolchain, but it was previously broken because it tried to use a
relative directory name rather than a relative target name.

I think this group will only ever be included when there's a bug in a GN
file that results in a target being included in the wrong toolchain.
That will now result in an `assert(is_fuchsia)` failing somewhere, which
is more helpful than a red herring "Unable to load <path>/BUILD.gn"
failure, which is what would happen before this fix.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/750352
Original-Revision: 967ebdcb2f78fa1dcb14f0db9c75a32cfdf86737
GitOrigin-RevId: d8e0a5c77c0bc8f771f565424cb36019228386f4
Change-Id: I54229653ab3350f29586887740dbe64fd649172b
1 file changed
tree: 37508d00f8017fd00904d8253d774592ddea474d
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.