commit | 436fef0c27a2242593f71cb1ba58c3a8c2269a98 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Tue Apr 12 01:25:48 2022 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 12 01:25:48 2022 |
tree | f807f9a2c357e9edb21ddb62332e05ce8e2363b5 | |
parent | 9c8fe0d0f5ef8117866b43436f9030d59b950798 [diff] |
[deploy] Leave a history record for "crashing" actuations. Assets aren't supposed to be handled by multiple actuators concurrently (currently this is enforced by LUCI Scheduler). If an actuator calls BeginActuation, it should eventually call EndActuation. If an asset "sees" two BeginActuation calls in a row, then the previous actuation most likely crashed. We should record this in the AssetHistory. R=ddoman@chromium.org, iannucci@chromium.org BUG=1301023 Change-Id: Ic35afaa4b507d7269fc861eb925a0a15e57232a9 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3583217 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:
fetch infra cd infra/go eval `./env.py` cd src/go.chromium.org/luci
Contributing uses the same flow as Chromium contributions.