[roll] Roll fuchsia [blackout] catch component stop error on teardown

If the test fails when the component isn't running for whatever reason,
this command will fail, which messes with the error reporting for the
real failure. This teardown is best effort anyway so it doesn't really
matter.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1109532
Original-Revision: 7786613b429f8e02ebdfdcb3ec64bc13d88381c0
GitOrigin-RevId: 60199c91b7188727b1aac8be8c5a9b9926457f62
Change-Id: I1482fbb0d0b645eba5be6fdfdb0bba8f12e10250
1 file changed
tree: 0a4a43e127b35aea3a45f914c894f5168f5aadaa
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.