[roll] Roll fuchsia [ffx] Determine RCS state in target list (reland)

When running `ffx target list` when discovery is turned off
in the daemon, we discover devices locally. This CL adds the
next requirement, which is to try to connect to RCS, and get
get the product/board information.

(Added in reland) Timeout (default: 10 seconds; configurable
via "target.host_pipe_ssh_timeout") if there is no response from a
target, in which case report "unknown" for RCS and product.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1036333
Original-Revision: 69e1910e8e02b0c6ae15846f56aee4c7e13f40ae
GitOrigin-RevId: 55924dd4d6350b748984353bf2642416813771dd
Change-Id: I03bd90ee602c9f3f5827a7147fb76d58c1641f8f
1 file changed
tree: 9ae6bfb0614efdeeff8d5ce60cceb66b73e8ceeb
  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.