[roll] Roll fuchsia [realm-builder] handle relative URLs at runtime

If a dynamic component is added to a realm with a relative URL,
component manager may construct an absolute URL on top of a
`realm-builder://` URL and then ask the realm builder server to resolve
it. We can detect this situation by looking for URL fragments (ex:
`#meta/foo.cm`) and then pulling up the requested manifest from the
test's package.

Original-Fixed: 85884
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/592964
Original-Revision: 96266e11e9f1729e529fcde31495f727a7cb709f
GitOrigin-RevId: 1746ded25b2538bcb64230aaff52f0505a8c722a
Change-Id: I0f668a3fa96abbc758355d90ba53e0729d90e395
1 file changed
tree: b115c7fc0a09722f4f32b6f403aedfff6e670018
  1. infra/
  2. third_party/
  3. firmware
  4. flower
  5. jiri.lock
  6. minimal
  7. prebuilts
  8. README.md
  9. stem
  10. test_durations
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.