update vagrant to use 2048MB ram on Windows #392
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
miller-time
force-pushed
the
windows-vagrant
branch
from
eaed74d
to
dd48e54
Compare
miller-time
force-pushed
the
windows-vagrant
branch
from
dd48e54
to
531f47b
Compare
miller-time
force-pushed
the
windows-vagrant
branch
from
531f47b
to
6913390
Compare
miller-time
force-pushed
the
windows-vagrant
branch
from
6913390
to
39ec2fd
Compare
|
This is obsoleted by #432, I don't think docker has an explicit memory limit. |
|
even better, thanks! I'll have to try it out with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cargo buildran out of memory when it was set to 1024