please reclaim the existing 24 32-bit linux trybots on tryserver.chromium.linux |
||||||||
Issue description
The Linux x86 (32-bit) version of Chrome is no longer shipped, and while we still want to support 32-bit builds, we only want to support building (and running) them on a 64-bit host install.
So, can we please re-image the existing 32-bit bots, or swap in 23 new GCE machines for them? We should use the standard 64-bit image. We can use either Precise or Trusty, whichever is easier and more convenient for labs folks.
Once we're done re-imaging these and the two remaining 32-bit bots on chromium.linux, we can toss the weird old process we had for configuring 32-bit bots.
The existing pool of slaves is:
linux_32_slaves = [117, 162, 163, 188, 193, 196, 198, 201, 203,
211, 227, 260, 338, 786, 787, 788, 804, 822,
824, 825, 826, 827, 828]
% vm%d-m4 .
from
https://code.google.com/p/chromium/codesearch?q=tryserver.chromium.linux%2Fslaves.cfg#chromium/build/masters/master.tryserver.chromium.linux/slaves.cfg&l=143
and also vm897-m4 from
https://code.google.com/p/chromium/codesearch?q=tryserver.chromium.linux%2Fslaves.cfg#chromium/build/masters/master.tryserver.chromium.linux/slaves.cfg&l=77
It's probably easier for non-labs folks if we get a new pool of machines, so I don't have to worry about things being broken or messing with the Chromium CQ, but if for some reason we need to re-image them in place, we can make that work, too.
,
Apr 7 2016
,
Apr 12 2016
Dirk, gce based vm's o.k?
,
Apr 12 2016
Yup, GCE would be fine, but as per https://bugs.chromium.org/p/chromium/issues/detail?id=600904#c4 I think we can just move the builders onto the existing 64-bit CQ pool since linux_blink_oilpan_rel is gone now, and then we can just reclaim these. So, same deal, I'll move the existing builders and then re-assign back to you to reclaim.
,
Apr 20 2016
,
Apr 26 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build.git/+/7923ac5efd20a03bc6d5578617ae21c6fb538789 commit 7923ac5efd20a03bc6d5578617ae21c6fb538789 Author: dpranke@chromium.org <dpranke@chromium.org> Date: Tue Apr 26 22:21:48 2016 This moves all of the remaining 32-bit linux builders onto 64-bit machines. The last phase of cleaning up the Linux 32 configs is to replace the builders and testers with normal 64-bit machines; we no longer wish to support the weird '64-bit kernel with 32-bit userspace' configs that we had before. The waterfall bots are repurposed valgrind machines. The tryservers are moved into the existing optional pool of machines, since they won't be used often. R=thestig@chromium.org BUG= 600903 , 600904 , 590004 Review URL: https://codereview.chromium.org/1917883003 git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/build@300213 0039d316-1c4b-4281-b951-d872f2087c98 [modify] https://crrev.com/7923ac5efd20a03bc6d5578617ae21c6fb538789/masters/master.chromium.fyi/slaves.cfg [modify] https://crrev.com/7923ac5efd20a03bc6d5578617ae21c6fb538789/masters/master.chromium.linux/slaves.cfg [modify] https://crrev.com/7923ac5efd20a03bc6d5578617ae21c6fb538789/masters/master.tryserver.chromium.linux/slaves.cfg
,
Apr 27 2016
,
Apr 30 2016
These bots can be reclaimed now; I've migrated the builders to a different pool.
,
May 2 2016
,
May 2 2016
Is this a dupe bug? https://bugs.chromium.org/p/chromium/issues/detail?id=600904
,
May 2 2016
Looks like it. GO ahead and mark it as a dupe and I'll add the couple of missing ones to my cl.
,
May 2 2016
,
May 2 2016
Well, they were different sets of builders, so I didn't view them as duplicates, but as long as they get reclaimed, I don't much care how you track them :).
,
May 2 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome-golo/chrome-golo.git/+/2a510f9c5cb5025eccd59987e71b67743f67acf3 commit 2a510f9c5cb5025eccd59987e71b67743f67acf3 Author: pschmidt <pschmidt@google.com> Date: Mon May 02 20:43:06 2016
,
May 2 2016
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by dpranke@chromium.org
, Apr 6 2016