[roll] Roll fuchsia [netemul] Don't start a Sandbox that goes unused

If there are no network configurations for the runner, there's no need
to create a `TestSandbox`. This was caught due to error logs during a
bad teardown of an unused `TestSandbox` instance.

Original-Fixed: 105431
Multiply: netemul-runner-tests :50
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/705422
Original-Revision: cba56e5bceea4f518e0fccf11dff5cd872ebca03
GitOrigin-RevId: c7003a4d962817d687601131d9a0d2ea0bb430e5
Change-Id: Ic0f8109c70f24b4c7f2b364c0aea3dc98a5455ae
1 file changed
tree: c1384df8b7a234261cc522e65f9cb9ebf189e934
  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.