[roll] Roll fuchsia [emu] Fix --reuse semantics

The attached bug called out an unanticipated change in the semantics of
--reuse; when the instance did not already exist, the new semantics
would fail the launcher instead of creating the new instance.

This CL adds a new EngineOption type as output for get_engine_by_name,
such that callers can distinguish between failing to retrieve an
existing instance and that instance simply not existing. Now, if the
instance didn't exist before the start call with --reuse, we notify the
user, revert the --reuse flag so that the instance can be properly
initialized, and then continue the start sequence.

Original-Bug: 118006
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/786441
Original-Revision: 3bf1bec8930695fb771385f1f064219d01de5db4
GitOrigin-RevId: 0371b0e3c145f1ece6ab71e112b150974d87d793
Change-Id: I5345fddc662a0073a719f5e1d5f3a8d9b5a14feb
1 file changed
tree: 4940aca68bf1bdd231c1ae40939ce5f3236e52fe
  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.