Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hack to add more latent builders in case of ill-timed restart #195

Merged
merged 1 commit into from Jan 12, 2016

Conversation

@larsbergstrom
Copy link
Contributor

larsbergstrom commented Jan 12, 2016

We should never have more than two active, but when one builder "dies" for w/e reason, for the duration of the buildbot run, the machine will not be restarted. This adds 3, getting us to 5, an arbitrary number that I hope will keep us at our 2 live instances at any point in time until we can either pull the trigger on reserved instances or get better about Graceful Shutdown, etc.

Also, removed servo-linux1, which is no longer around but was still on the waterfall page.

r? @edunham @metajack @Manishearth

Review on Reviewable

…estart. Also cleanup list.
@larsbergstrom
Copy link
Contributor Author

larsbergstrom commented Jan 12, 2016

Aha, this will create more than 2 live instances in the case where there is both a real build and a try build going at the same time.

@metajack
Copy link
Contributor

metajack commented Jan 12, 2016

I'm not a huge fan of this, since it will make the real problem harder to debug and easier to ignore.

@metajack
Copy link
Contributor

metajack commented Jan 12, 2016

@bors-servo r+


Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.


Comments from the review on Reviewable.io

@bors-servo
Copy link
Contributor

bors-servo commented Jan 12, 2016

📌 Commit adc255d has been approved by metajack

@bors-servo
Copy link
Contributor

bors-servo commented Jan 12, 2016

Testing commit adc255d with merge a18eb67...

bors-servo added a commit that referenced this pull request Jan 12, 2016
Hack to add more latent builders in case of ill-timed restart

We should never have more than two active, but when one builder "dies" for w/e reason, for the duration of the buildbot run, the machine will not be restarted. This adds 3, getting us to 5, an arbitrary number that I hope will keep us at our 2 live instances at any point in time until we can either pull the trigger on reserved instances or get better about Graceful Shutdown, etc.

Also, removed `servo-linux1`, which is no longer around but was still on the waterfall page.

r? @edunham @metajack @Manishearth

<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/195)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Jan 12, 2016

☀️ Test successful - travis

@bors-servo bors-servo merged commit adc255d into servo:master Jan 12, 2016
2 of 3 checks passed
2 of 3 checks passed
code-review/reviewable Review in progress: 0 of 1 files reviewed, all discussions resolved
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
homu Test successful
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.