[roll] Roll infra/recipes [validate_lucicfg] Retry the race condition check

Retry the check for deployment race conditions. This minimizes the
number of times the change owner is added to the attention set when a
stack of change is approved at once by waiting a reasonable amount of
time for luci-config to pick up the previous change.

Most of the time the first attempt will pass, but a couple times a day
this will result in a lucicfg run that blocks for 15 or so minutes. This
seems acceptable.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1509846
Original-Revision: e166944b64bac11d2ff8daa8b60c1e0751ae2530
GitOrigin-RevId: 4d2db9099644c3aa0d13ca12775d0fac2d77acea
Change-Id: I4abe0f6b6a32f24c0d1e95e2cb69e0ef517d04f2
1 file changed
tree: dda93356e177e86da6e790e18d7120cf6b3d0cfd
  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.