[roll] Roll infra/recipes [auto_roller] Handle force-submit dry run retries

Previously, a dry-run force-submit roller would fail if it found a
previous identical roll attempt, when trying to determine whether CQ
passed or failed, because rollers don't run CQ at all in force-submit
mode. Now, we'll skip looking up past CQ dry run statuses in
force-submit mode.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/454642
Original-Revision: 3edb99e006b3915daf1ad4420d501a43fdf5160d
GitOrigin-RevId: 332f838bad8d1635ad5a9c838e460bb5d3b23863
Change-Id: I618e90ca28d7eebc328117fb0062381ce0af58a7
1 file changed
tree: fd0b6a1f7664f4345ce03a66fca1c905b6451059
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. flower
  8. jiri.lock
  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 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.