[roll] Roll fuchsia [netconform] Explicitly tell ffx symbolizer path

Network conformance tests are failing in CI due to `ffx log` not finding
the SDK (which it needs for the symbolizer tool). Add in-tree test
coverage for this and add an explicit dependency on the symbolizer tool
and its SDK metadata via populating our own SDK manifest for our
isolated FFX instance.

Test: conformance_emulator_test
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/897258
Original-Revision: e8fe283678003c46e02d85487b281dd54e37d748
GitOrigin-RevId: dc7e9bf4c686e8f02559c48ee7509c62a307ec33
Change-Id: I58bc177f86e2206641eec268ee175c1ad7fdf6e4
1 file changed
tree: d4f2b4655182453d2b985eb6bcd387190c730b42
  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.