[roll] Roll fuchsia [emu] Add testing around control sequence of start

This CL adds more tests to the emulator start subcommand, specifically
in the domain of the start command's control sequence. It verifies that
the dry-run, stage, and edit flags interact correctly with the config,
reuse, and verbose flags and that changes in each stage are correctly
propagated to the final start Command.

In writing these tests, we uncovered an as-yet undetected bug in the
--edit flag behavior that was actually losing the user's modifications
before launching the emulator instance. That has been addressed in this
CL as well.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/789729
Original-Revision: 198463783e21fa862ef2fbb04b0c2bdaa31faa54
GitOrigin-RevId: 16362c2e7da7cc073e0e1d3ce9dee9f5fffb9f37
Change-Id: I6f777218225230e915827ea796264114fa03ab5f
1 file changed
tree: 7d5bc8d543275c3ca746c2708fc60ab2d0912709
  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.