vm677-m1 needs to run "annotated" XOR "remote" run builds. |
||||||||
Issue descriptionHaving both "annotated_run" and "remote_run" builds on the same builder uses effectively twice the disk space for caches and other objects, and is causing "vm677-m1" to run out of space. https://uberchromegw.corp.google.com/i/chromium.webrtc.fyi/buildslaves/vm677-m1 Currently, the builder runs: Mac Builder (remote_run) ios-device (annotated_run) ios-simulator (annotated_run) We need to either: 1) Convert "ios-device" and "ios-simulator" to remote_run. - smut@, correct me if I'm wrong, but this should be easy since I did the legwork a few weeks back for "ios-simulator" elsewhere? 2) Split this builder into two buildslaves, one for each. Thoughts?
,
Jun 9 2017
I would vote for 1
,
Jun 9 2017
Sure I think remote_run will just work. P.S. I receive crbug email on smut@chromium.org I just can't sign in with it so ccing either on bugs is fine. P.P.S. Common English "or" already means exclusive or. Exhibit A: From Merriam-Webster [1], "used as a function word to indicate an alternative". All of the examples here are exclusive or: "coffee or tea sink or swim, the equivalent or substitutive character of two words or phrases lessen or abate, or approximation or uncertainty in five or six days". [1] https://www.merriam-webster.com/dictionary/or
,
Jun 10 2017
I suppose you have to know your audience. For example, if you ask me "coffee or tea", and "coffee" is true, I'll not even bother evaluating the "tea" option.
,
Jun 12 2017
I've already filed a ticket (bug 731594) for getting a new machine since we ran out of disk space (even if all used the same checkout, which may not have been true due to the remote_run/annotated_run combo). After moving the iOS builders to the new VM it will not mix anymore. The only reason I used annotated_run for these bots was that all other iOS bots were doing that, and I didn't want to risk a broken bot (nor do I have the time to upgrade all the other ones, smut@ is the right person for that effort).
,
Jun 12 2017
Since this isn't solved, and it needs to be solved, I don't think it should be closed. I'll block it on the bug that you linked, though.
,
Jun 12 2017
Fair enough, but I don't think it needs to be on the trooper's triage list. That's why I closed it. I can own it until fixed.
,
Jun 19 2017
We're back to only one builder at this VM, so it's resolved.
,
Jun 23 2017
,
Jun 23 2017
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by iannucci@chromium.org
, Jun 9 2017