New issue
Advanced search Search tips

Issue 646726 link

Starred by 1 user
Status: Fixed
Owner:
friedman@chromium.org
Closed: Sep 2016
Cc:
d...@chromium.org
vhang@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Buildbot masters are still running on master2

Project Member Reported by dsansome@google.com, Sep 14 2016 
Are they supposed to be?  Is the machine even supposed to be up?

Here's a list of running masters: http://shortn/_rfM5dI67Zf
Project Member

Comment 1 by sheriffbot@chromium.org, Sep 14 2016

Labels: Hotlist-Google

Comment 2 by fried...@google.com, Sep 14 2016

Cc: -friedman@chromium.org d...@chromium.org
Owner: friedman@chromium.org
Status: Assigned (was: Untriaged)
Something must have started them back up... mastermanager or a trooper?

I left this host up after the migration just in case something went wrong.  It can be decommed now I think.

Comment 3 by d...@chromium.org, Sep 14 2016 

Yeah that's definitely not right. Go ahead and decommission; as far as I know, nothing uses master2 anymore.

Comment 4 by friedman@chromium.org, Sep 15 2016

Status: Fixed (was: Assigned)
Project Member

Comment 5 by bugdroid1@chromium.org, Sep 15 2016 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome-golo/chrome-golo.git/+/a9ea2987c163b0b8fa1670f4f05d607bd5cacb7e

commit a9ea2987c163b0b8fa1670f4f05d607bd5cacb7e
Author: friedman <friedman@google.com>
Date: Thu Sep 15 21:09:31 2016
►

Sign in to add a comment