Travis-CI integration #20
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
|
Withdrawing this PR, because the improvements I've made are probably too thorough to merge into a project without much heavier active maintenance. Instead, I've forked the relevant parts into https://github.com/Pr0methean/betterrandom. |
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.
Fixes #18
This is one of the cherrypicks of #16. It updates Cobertura, breaks out the dieharder dependency to /usr/bin so that it's more cross-platform (still won't work on MinGW or naked Windows), switches DiehardInputGenerator to use a named pipe to reduce disk space requirements, and splits the Dieharder suite into two so that it'll finish within a free Travis-CI.org instance's timeout. It also decreases the number of bytes demanded from random.org.
Branch coverage is currently below spec at 93.4%, even though all the code I've touched for this test has full branch coverage! Possibly some exception-handling code in RandomDotOrgSeedGenerator is no longer being exercised now that we're not overusing the service?