[roll] Roll fuchsia [network/tests] Document orderly shutdown

Remove TODOs to make orderly shutdown in netemul tests automatic or
unnecessary. There is a well-documented `TestRealm::shutdown` method
that is applied consistently in integration tests that involve several
networking components, and requiring the test author to decide whether
to invoke it can be useful since it gives us a good signal about
potential race conditions during interface removal, etc.

Original-Fixed: 92164
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/727767
Original-Revision: 4b36fd89f76c788e4dd4245f49a876a40f53de18
GitOrigin-RevId: cd56d0b6d6d7d7497aea601fc4ed42868fb30168
Change-Id: If36980aec6a35cf2773dabf50e88ae307635dac8
1 file changed
tree: cbb4df23bb94b2f43797f4db9053989f83217fbe
  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.