commit | 9ca1d4472e8fd0b395a89231f3a09c8ca22b1248 | [log] [tgz] |
---|---|---|
author | Scott Lee <ddoman@chromium.org> | Wed Dec 01 19:56:46 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 01 19:56:46 2021 |
tree | 6db70c513b15371ca75ee8311d5783a81e16e9bf | |
parent | a7acd6643beb88b7f78fb0d7105d105b06923c4c [diff] |
[buildbucket] add MaxAgeScheduled in metric This CL ports the V1 metric, and adds a V2 equivalent. Note that PyBB and GoBB will compute and report the data individually, once this CL is landed. However, all the alert and dashboard configs use m.Max(). Therefore, it should be ok to have the duplicate data temporarily. Once the data correctness is checked, PyBB will be updated to stop computing MaxAgeScheduled. Bug: 1249664 Change-Id: I45d93069b9b53e518fcf9cba73ad0c712d8dc3f2 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/3299391 Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by: smut <smut@google.com>
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.