[roll] Roll fuchsia [wlan][test] Failing to start a trace counts as a test failure Tracing some WLAN tests is critical to debugging their failures, especially when the failures are intermittent. Future changes that preclude starting a trace will cause some tests to fail. This is limited to hw-sim and drivers-only tests. Note this does not prevent the failure to collect a trace or collecting an empty trace. These tests have likely never failed since trace_manager and its associated capabilities have always been routed correctly. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1423274 Original-Revision: 1f1fb19fd405ccbe647237553cdffead58278c11 GitOrigin-RevId: 533d2db946dcd6b9189e33e9e2fb726ece226ef2 Change-Id: I557f894cb1863ddc20c917707a1dd75f95772371
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 in one of the communication channels documented at get involved.
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.