New issue
Advanced search Search tips

Issue 699782 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Remove WPTServe builders on chromium.fyi.

Project Member Reported by qyears...@chromium.org, Mar 8 2017

Issue description

These were added last year for bug 581386 and bug 620871, and now they shouldn't be necessary since wptserve is turned on by default now.

I think that this will involve updating the relevant configs in build and src repos, and then telling the right people that the slaves are not needed.
 
Owner: jeffcarp@chromium.org
Status: Started (was: Available)
Owner: qyears...@chromium.org
Omg my bad >_< thought this would be a helpful thing to pick up then just saw your CL https://chromium-review.googlesource.com/c/452860
Sorry about not updating the bug earlier :-/

(Next step after that is to remove entries in src/tools/mb/mb_config.pyl and ask for the slaves to be marked as unused or turned off or something like that.)
Cc: d...@chromium.org dpranke@chromium.org
dba@, is there anything we should do for slaves that are now unused? Specifically, the following slaves are now unused:

 slave72-c1
 vm114-m1
 vm115-m1
Project Member

Comment 7 by bugdroid1@chromium.org, Mar 14 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ec06dfef6be7f6c1dce6ecf841089863528fa05f

commit ec06dfef6be7f6c1dce6ecf841089863528fa05f
Author: qyearsley <qyearsley@chromium.org>
Date: Tue Mar 14 21:15:58 2017

Remove WPTServe FYI bots from mb_config.pyl.

BUG= 699782 

Review-Url: https://codereview.chromium.org/2746243003
Cr-Commit-Position: refs/heads/master@{#456832}

[modify] https://crrev.com/ec06dfef6be7f6c1dce6ecf841089863528fa05f/tools/mb/mb_config.pyl

Comment 8 by d...@chromium.org, Mar 14 2017

Re #6 - We can reclaim the unused bots once they've been removed from slaves.cfg and the master has been restarted.
Ah, excellent! Now I'm pretty sure that the master has been restarted after having removed them, since the builders are not listed at https://build.chromium.org/p/chromium.fyi/builders/ -- so the slaves listed in #6 can be reclaimed :-)
Project Member

Comment 10 by bugdroid1@chromium.org, Mar 20 2017

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

commit ef2c2bb74c03a324f772a2ba6fb2589d93d6e807
Author: Bryce Albritton <dba@google.com>
Date: Mon Mar 20 22:04:25 2017

Project Member

Comment 11 by bugdroid1@chromium.org, Mar 20 2017

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

commit ef2c2bb74c03a324f772a2ba6fb2589d93d6e807
Author: Bryce Albritton <dba@google.com>
Date: Mon Mar 20 22:04:25 2017

Comment 12 by d...@chromium.org, Mar 20 2017

The following have been reclaimed:

slave72-c1
vm114-m1
vm115-m1


Status: Fixed (was: Started)
Thanks :-)
Project Member

Comment 14 by bugdroid1@chromium.org, Mar 20 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/d77c88dc8da2876e7d78cd7f2509d363c9f4e339

commit d77c88dc8da2876e7d78cd7f2509d363c9f4e339
Author: Bryce Albritton <dba@google.com>
Date: Mon Mar 20 22:08:02 2017

Sign in to add a comment