[roll] Roll fuchsia [network/testing] Route dev-class-network directory to test collection This missing capability was causing network-conformance tests to fail because network-test-realm was unable to move interfaces into the hermetic network realm. We only started tripping over this after switching to the netdevice-migration version of the virtio driver (https://fxrev.dev/Id532ddbc5d95d089ace1493ee5de26805a1029a7). The existing NTR integration tests didn't catch this because netemul doesn't use src/connectivity/network/meta/test-collection.shard.cml as part of routing capabilities to components under test. As put by peterjohnston@google.com, "In the NTR integration tests, the NTR is not included as part of the network realm like it is when it's used in "production"; it's tested in isolation from the rest of the system, and /dev/class/{network,ethernet} are routed to it from the netemul sandbox." Original-Bug: 94758 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/685743 Original-Revision: af4ad69579c4693849c2c4de0449a370c85c128c GitOrigin-RevId: b268d9276a8439eecb81f95de14df6367c16bd2e Change-Id: Ifec943a55c59fedd19c72b882ca955da9dd9ba7e
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.