New issue
Advanced search Search tips

Issue 821257 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Migration app does not close bugs

Project Member Reported by no...@chromium.org, Mar 13 2018

Issue description

Milo API recently changed to include swarmbucket builders in GetCompressedMasterJSON API. As a result, builders never disappear and never marked as migrated in migration app.

We have two ways of solving this:
- specify "turn off emulation" when calling GetCompressedMasterJSON. Implement the parameter too
- change status to Migrated when we see that the Buildbot bulider is no longer getting builds, e.g. we haven't seen builds for a week or something

WDYT?

 
Both look ugly :(

How about not solving this and instead changing docs to say that bug must be closed manually once builder is migrated?

Comment 2 by hinoka@chromium.org, Mar 13 2018

Yeah closing manually doesn't seem like a big deal, considering it should be happening right after a person commit some CL and bugdroid pings on it.

Comment 3 by estaab@chromium.org, Mar 13 2018

Status: Available (was: Untriaged)
Doesn't the app have re-open logic? If not, manual close sounds good to me too.

Comment 4 by no...@chromium.org, Mar 13 2018

app does not have re-open logic.

just closing a bug manually is not sufficient, because the app tracks migration state too. We can change the app to sync migration state of a builder in datastore to status of the corresponding bug, i.e. bug closed => builder is marked migrated in the app. How does that sound?

Comment 5 by no...@chromium.org, Mar 19 2018

Status: WontFix (was: Available)
in a meeting, we've accepted proposal in comment 4.
I will send a PSA.

Comment 6 by no...@chromium.org, Mar 19 2018

feature request to sync with bugs: issue 823541

Sign in to add a comment