[roll] Roll fuchsia [fshost] Ensure a new volume is used for flashing blob images

When a previous flash attempt is interrupted, we would keep the volume
around until the next installation attempt. This means that the
components actually flashing the image would end up overwriting ranges
of an existing file on disk. This was resulting in 40 MiB chunks taking
30-60 seconds to flush, until a compaction ran in the background on the
pending volume.

To avoid that slowdown, we always reprovision the pending volume when
this method is called. This is okay since it only is used from the
fastboot component before writing out a new system image.

Test: fx test system_volume_manipulation
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1533746
Original-Revision: fde6aa929f9a5139a7a02e7a2fc4ceddddfcc9a3
GitOrigin-RevId: 8c2a63da2ac5c89c8069b055b1744a6798e7ef51
Change-Id: Id3e73f12996dcaa6f63af31feefe22f0e43b11aa
1 file changed
tree: 169d01215522ffaa1174272c9b68ff8e1a39007d
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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 in one of the communication channels documented at get involved.

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.