Reduce cargo test parallelism. #318
Merged
+2
−2
Conversation
This file contains hidden or 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
It looks like `cargo test` is getting SIGKILL'ed on travis and I'm not sure why. One possibility is that it's running out of memory. Try to fix this by reducing the number of jobs `cargo test` does in parallel.
|
@bors r+ |
|
📌 Commit e915a27 has been approved by |
bors
added a commit
that referenced
this pull request
Jan 2, 2017
Reduce cargo test parallelism. It looks like `cargo test` is getting SIGKILL'ed on travis and I'm not sure why. One possibility is that it's running out of memory. Try to fix this by reducing the number of jobs `cargo test` does in parallel.
|
☀️ Test successful - status-appveyor, status-travis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It looks like
cargo testis getting SIGKILL'ed on travis and I'm notsure why. One possibility is that it's running out of memory. Try to fix
this by reducing the number of jobs
cargo testdoes in parallel.