[roll] Roll fuchsia [bt][tests][bootstrap] Don't invoke Access.WatchPeers from tests fuchsia.bluetooth.sys/Access.WatchPeers is a hanging get method that fails if invoked more than once before a prior invocation has returned. The AccessHarness continually watches this method to update its internal peer state. A test in the bt-bootstrap-integration-tests also invoked WatchPeers on the same AccessProxy (exposed via the harness' auxiliary state). In unlucky (i.e. flaky) situations, the test code and Harness invocations would coincide, leading to test failure. Instead, check the initial state of the AccessHarness' peers via the Expectable interface, and add an AccessWrapper to wrap the FIDL proxy, which will prevent test code from directly invoking WatchPeers and reintroducing flakes. Also, WatchPeers is called once during Access Harness initialization to ensure the initial peer state is accurate. MULTIPLY: bt-bootstrap-integration-tests (fuchsia): 100 Original-Bug: 92092, 91855 Test: Ran the bootstrap integration tests 500x locally without failure. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/648446 Original-Revision: 985185e6642ce154857040ded5ae8f064c02d802 GitOrigin-RevId: ff8abddab161809d9809235f81c34c5192ce844f Change-Id: I3e710936ed9a82162edb35b59dd35f842975d40a
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.