[roll] Roll fuchsia [component_manager] Remove invalid state from StartedInstanceState

Someone could repeatedly call StartedInstanceState::set_program, or call
other methods and later StartedInstanceState::set_program. These are
never exercised in production and doesn't make sense to support. By
tweaking the StartContext we can avoid first creating a pending runtime
and then later set a program. Instead, once created the
StartedInstanceState either has a program or it doesn't.

After this, the make_execution_runtime method becomes a random
hodgepodge of checks. That's simply inlined into do_start.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1030787
Original-Revision: 5e7df04fd6002fc3412b71eb94c94c19ec5ee438
GitOrigin-RevId: f235bf62d814d4fc24895c6cd45ece2601fb7e0f
Change-Id: Ifa5e186354fea40902998b1f947e4d4957255712
1 file changed
tree: 339523bc8c183ff914b337d7d92841b8fc8dc825
  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.