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

Issue 720145 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

buildbucket_lib should 'raise' on an API error result.

Project Member Reported by dgarr...@chromium.org, May 9 2017

Issue description

buildbucket_lib currently assumes that a return code of 200 means that the API request was successful.

This is not true (see  crbug.com/720119 ).

There are currently cases where we ignore error responses from the API (such as when scheduling builds). There are other places where the users of buildbot_lib examine the API response to see if there was an error.

To be more straight forward and more consistent, we should raise an exception whenever we get a 200 response code, and the json response contains an 'error' key.

We can attach the details of that json response to the exception for clients that need it.

 
Status: Started (was: Untriaged)

Comment 2 by aut...@google.com, May 16 2017

Labels: -current-issue
Status: Assigned (was: Started)
Labels: Hotlist-Fixit
This turned out to be a lot more complicated than I originally thought for a variety of reasons around how the API works.

https://chromium-review.googlesource.com/#/c/chromiumos/chromite/+/655760/
Status: Fixed (was: Assigned)

Comment 7 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 8 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)

Sign in to add a comment