[roll] Roll fuchsia [components] Fix early exit flake in attributed-logging-test This CL is just a copy of the other half of Yegor's Iceaed7b755013d22dc7516499a048e8e548821b9. c.f. the relevant description: Component manager uses the component's ComponentRuntime in `with_logger_as_default` to log the routing error with attribution. When the component exits immediately after causing a routing error, the ComponentRuntime is destroyed, so component manager logs it using its own, unattributed logger. The workaround is to keep the components alive for the duration of the test and exit the test only when it sees all the expected logs. Multiply: fuchsia-pkg://fuchsia.com/attributed-logging-test#meta/e2e-test.cm Original-Fixed: b/320698181 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1017433 Original-Revision: bbd95bcc49de916d3749a3a41ceb693d26d3ac57 GitOrigin-RevId: 68deb50eae3bfeccdba36b3e2d7f89744db94d5a Change-Id: Icdb4fad061a606b043763c29c5c3dc6e4adc9b82
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.