cros132-c2 blocking umaro-release builder on R52. |
||||
Issue descriptionCurrently, the release waterfall is using the GCE instance cros132-c2 as the master builder for the R52 branch. However, that IP address was expected to be available for ccompute, and is blocking the creation of "cros-beefy158-c2", which is assigned to the builder for umaro-release. We should remove cros132-c2 and replace it with a cros-wimpy builder. This will require another chromeos-releases waterfall restart. I'm not sure why cros132-c2 was still around. I must have missed it when cleaning up the old GCE builders.
,
May 26 2016
,
May 26 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/infradata/master-manager.git/+/46efa08acea6a3c016930be47dbdfcecca591c2f commit 46efa08acea6a3c016930be47dbdfcecca591c2f Author: dgarrett <dgarrett@google.com> Date: Thu May 26 21:50:41 2016
,
May 26 2016
The release master for %52 was reassigned to cros-wimpy6-c2, cros132-c2 was deleted, and cros-beefy158-c2 has been created. Everything should be happy on this front, going forward.
,
Jun 17 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/tools/build/+/6ecbddae7fdfda01d0efdffd90d68c43a89041d8 commit 6ecbddae7fdfda01d0efdffd90d68c43a89041d8 Author: dgarrett <dgarrett@google.com> Date: Thu May 26 21:31:55 2016
,
Jun 27 2016
Closing... please feel free to reopen if its not fixed.
,
Jun 27 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by dgarr...@chromium.org
, May 25 2016