[roll] Roll fuchsia [netemul] Start driver test realm lazily

Move driver test realm initialization to network-context instead so it
can start it only when needed.

This should help prevent occasional error logs from driver test realm in
tests that don't create devices, and probably reduce some overhead as
well.

Use FX_PLOGS for status logging while I'm here.

Original-Fixed: 91204
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/634282
Original-Revision: 8b5f623fbb4421837b952c6fab2fe953725ad0dd
GitOrigin-RevId: fd3144472b278e5214cfa0d12ee3db8b6e6659a3
Change-Id: Id09cf66788fc2a6439c6dc9e0016291a85b4ba09
1 file changed
tree: dc9c19df51a016d6e3c74c88cf2c99c9e29e65de
  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.