[roll] Roll fuchsia [netemul] Define and parse network config

Until the component manifest schema supports it, the network
configuration for a netemul runner test will be specified in a separate
JSON file bundled with the test package.

Also, this CL does not introduce the actual configuration logic that
will exercise the netemul sandbox and the configurable netstack; it just
introduces the configuration schema and reads and validates it in the
runner.

Original-Fixed: 92175
Test: fx test netemul-runner-unit-tests
Test: fx test netemul-runner-tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/638601
Original-Revision: 1fd47b7fd1a049bab7b6b7e9a7b7c75ba9b88e72
GitOrigin-RevId: 036ea658581befacfe74e6c357eb93c6f46a6833
Change-Id: I8c50af8c1278b23884357424b935f370988a7939
1 file changed
tree: d4e06da2b05a20db0cff7d6c13a9d4a94a786d74
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.