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

Issue 648745 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug

Blocking:
issue 648728



Sign in to add a comment

Retrieve the most recent completed build cycle of a given buildbot on Waterfall

Project Member Reported by st...@chromium.org, Sep 20 2016

Issue description

After mapping from a CQ trybot to a Waterfall buildbot, we could start with the most recent completed build in the matching Waterfall buildbot. The build could be a failed or passed one, but not one with exception in which some step might not run.

There might be some possible optimization that we could start at an earlier build of the waterfall buildbot.


https://build.chromium.org/p/MASTER_NAME/json/builders/ provides information for this, but there might be a better API.
 

Comment 1 by st...@chromium.org, Sep 20 2016

Blocking: 648728
Project Member

Comment 2 by sheriffbot@chromium.org, Oct 5 2016

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by st...@chromium.org, Oct 5 2016

Cc: chanli@chromium.org lijeffrey@chromium.org
Owner: st...@chromium.org
Status: Assigned (was: Available)

Comment 5 by st...@chromium.org, Oct 7 2016

Status: Fixed (was: Assigned)

Sign in to add a comment