When a builder has > 100 pending builds, Milo displays 0 running builds (even if there are some running) |
|||||||
Issue descriptionI think this happens because swarming works on the builds from oldest to newest, but milo queries the pending builds from newest to oldest. Thus it never sees the in-progress builds in its query.
,
Jan 19 2018
,
Jan 19 2018
,
Jan 19 2018
The following revision refers to this bug: https://chromium.googlesource.com/infra/luci/luci-go.git/+/6febe0e669d2250ee82444be02bffb1f5d279559 commit 6febe0e669d2250ee82444be02bffb1f5d279559 Author: Nodir Turakulov <nodir@google.com> Date: Fri Jan 19 04:08:57 2018 [milo] load started and scheduled builds separately R=iannucci@chromium.org Bug: 803702 Change-Id: Icbb599aa06eea271c38487e479ad231b3c0451e8 Reviewed-on: https://chromium-review.googlesource.com/874787 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> [modify] https://crrev.com/6febe0e669d2250ee82444be02bffb1f5d279559/milo/buildsource/buildbucket/builder.go
,
Jan 19 2018
,
Jan 30 2018
,
Jan 30 2018
,
Feb 28 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by iannucci@chromium.org
, Jan 19 2018392 KB
392 KB View Download