New issue
Advanced search Search tips

Issue 882638 link

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



Sign in to add a comment

Recycle 10 Mac builbot builders to LUCI builders to ensure the LUCI Mac builder can keep up with the commits rate

Project Member Reported by nednguyen@chromium.org, Sep 10 
The mac LUCI builders are very behind compared with the buildbot builders (see https://ci.chromium.org/p/chrome/g/perf-side-by-side/console)

Vince: can we have 10 more 8 cores mac in chrome-swarming server to add to the LUCI builds?

An example existing spec of perf Mac LUCI builder: 
https://chrome-swarming.appspot.com/bot?id=vm142-m7&sort_stats=total%3Adesc

Comment 1 by nednguyen@chromium.org, Sep 11 

Hmhh, actually we still have a bunch of spared Mac minis with 4 cores. John: do you think it's ok to add those to Mac LUCI builders even though they don't have same number of cores compared with existing ones (I would just need to remove the cores dimension).

This is a bit urgent since the Mac perf builder is 1 day behind :-(

Comment 2 by nednguyen@chromium.org, Sep 11

Cc: jo...@chromium.org
I just turn down the mac buildbot builders in https://chromium-review.googlesource.com/c/chromium/tools/build/+/1220586. We now have 20 extra Mac machines available.

Lab: can you recycle vm{157..166}-m1 (10 machines total) & put them in the chrome-swarming server?

Comment 3 by nednguyen@chromium.org, Sep 11

Summary: Recycle 10 Mac vms to LUCI builders to ensure LUCI Mac builder can keep up with the commits rate (was: Add 10 more Mac LUCI builders to keep up with the commits)

Comment 4 by nednguyen@chromium.org, Sep 11

Summary: Recycle 10 Mac builbot builders to LUCI builders to ensure the LUCI Mac builder can keep up with the commits rate (was: Recycle 10 Mac vms to LUCI builders to ensure LUCI Mac builder can keep up with the commits rate)

Comment 5 by jo...@google.com, Sep 11

Cc: vhang@chromium.org
Owner: jo...@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 6 by bugdroid1@chromium.org, Sep 11 

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

commit 8c66bcd583a36f64020f668632396f16ad582ec8
Author: John Weathersby <johnw@google.com>
Date: Tue Sep 11 21:42:38 2018
Project Member

Comment 7 by bugdroid1@chromium.org, Sep 11 

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

commit bb52a4129f91c707d93b8331120fee1cb7269d58
Author: John Weathersby <johnw@google.com>
Date: Tue Sep 11 21:57:38 2018

Comment 8 by jo...@chromium.org, Sep 11 

vm{151..160}-m7 have been deployed and connected to private-swarming.

vm{157..166}-m1 have been reclaimed

Thanks.
Project Member

Comment 9 by bugdroid1@chromium.org, Sep 11 

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

commit 751f2bb158c1abc73e71415b753f218a1f3861c2
Author: John Weathersby <johnw@google.com>
Date: Tue Sep 11 23:20:37 2018
Project Member

Comment 10 by bugdroid1@chromium.org, Sep 11 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/afc09dc9b93c8112a3f8dc87574458649c6372fa

commit afc09dc9b93c8112a3f8dc87574458649c6372fa
Author: Nghia Nguyen <nednguyen@google.com>
Date: Tue Sep 11 23:35:06 2018

Comment 11 by nednguyen@chromium.org, Sep 12

Status: Fixed (was: Assigned)
Now we have 20 machines & the build seems to be catching up. Thanks John for the extremely quick fix!

Comment 12 by vhang@chromium.org, Sep 13

Labels: LUCI-Migration-Resources
►

Sign in to add a comment