[roll] Roll fuchsia [driver_test_realm] Wait for /dev/sys/test

The driver test realm binds a /dev/sys/test device during setup, but
this can be racy with the later teardown of the test realm.  If the test
completes quickly and the driver_manager starts to suspend, then the
later call to add the device will fail and emit an error log (which
fails unit tests).

Original-Fixed: 316579125
Multiply: devfs-test.cm
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/963955
Original-Revision: 106b353b380b3cebe15206429ac93e6b67ee4c8f
GitOrigin-RevId: 7ad97e3945025aa8180c4722215ecaff0b85564c
Change-Id: I5b094af4bec8d12a8056c97710b6d1c232351925
1 file changed
tree: b4c341429db2ffe1507d6416f344ebde12c224ef
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.