New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 808734 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

milo: console doesn't respect limit

Project Member Reported by no...@chromium.org, Feb 3 2018

Issue description

"Win7 Tests (dbg)(1)" is so slow, one build can span tens of commits. As of now, 
even with ?numbuilds=200, i can see only only 4 builds in
https://ci.chromium.org/p/chromium/g/chromium.win/console?numbuilds=200
and in
https://ci.chromium.org/p/chromium/g/migration-side-by-side/console?numbuilds=200

(why is it called numbuilds if the Y-axis is commits?)

this affects task force's ability to compare CI builders on LUCI to Buildbot. The side-by-side console is their main tool for that. They probably have to resort to builder view without by-commit alignment.
 
That's weird, it's being limited to 100 builds.  It shouldn't be doing that.

numbuilds is to match buildbot.  ?limit=100 also works.
Cc: tandrii@chromium.org
This situation should improve substantially with triggered builds ( Issue 794499 ).  The general question of disparity in builder rate does remain however. Do we have a sense for how large the range is between builders? Personally, I have indeed been using the builder views to compare Win7 Tests (dbg)(1).

It might be helpful if we could filter in/out builder pairs... not sure if it's worth the overhead though.
Labels: LUCI-Backlog
Owner: no...@chromium.org
Status: Assigned (was: Untriaged)
Nodir says he'll look into it because ?limit=200 isn't obeyed, likely in processing of gitiles.Log (only 100 comits show up).
Summary: milo: console doesn't respect limit (was: milo: console is not useful for slow builders)
(usefulness for slow builders or not would be a new feature; buildbot is also "not useful" in the same way.)

Comment 6 by no...@chromium.org, Feb 3 2018

Status: Started (was: Assigned)
Project Member

Comment 7 by bugdroid1@chromium.org, Feb 9 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/luci/luci-go.git/+/16245a7bfb80a739f09ef5e524d957baf79f402e

commit 16245a7bfb80a739f09ef5e524d957baf79f402e
Author: Nodir Turakulov <nodir@google.com>
Date: Fri Feb 09 02:43:14 2018

[milo] add paging to git.Log

Change git.Log()'s min parameter to "limit". Now it returns exactly the
requested number of commits, as opposed to >=min.

Add paging to git.Log to support limit>100

Bug:  808734 
Change-Id: I74ee7434be7d45318bf9d0881c737762fadf371a
Reviewed-on: https://chromium-review.googlesource.com/905636
Commit-Queue: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>

[modify] https://crrev.com/16245a7bfb80a739f09ef5e524d957baf79f402e/milo/frontend/view_console.go
[modify] https://crrev.com/16245a7bfb80a739f09ef5e524d957baf79f402e/milo/git/log.go
[modify] https://crrev.com/16245a7bfb80a739f09ef5e524d957baf79f402e/milo/git/log_test.go

Comment 8 by no...@chromium.org, Feb 12 2018

Status: Fixed (was: Started)

Comment 9 by efoo@chromium.org, Feb 28 2018

Labels: LUCI-Chromium-CQSets

Sign in to add a comment