[roll] Roll fuchsia [emu] Make target add timeout match start timeout

During a recent code review, I realized the ephemeral target timeout was
still a fixed 120 seconds. When running without KVM, we often encourage
folks to set the startup timeout to 360 seconds, which means they'll be
left waiting well after the ephemeral target has expired.

This CL matches the lifetime of the ephemeral target to the startup
timeout, so they should both complete at the same time (if it connects,
the ephemeral target becomes an MDNS target; otherwise they both expire
together).

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/736671
Original-Revision: e6bbee3beb9955cde86f589c7d1ccaf3c13343de
GitOrigin-RevId: 57580e787e03d23bbf2dc999ebdd0161f917fc50
Change-Id: I144c44c60ab23bc4fa1426f6098d86480425f54d
1 file changed
tree: 73a7b058343a2e1d7658513c648b071cea18d0d2
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.