Don't open bin/createcoverage results in browser #44
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
Update readme
|
Changes Unknown when pulling 97c70ed on instification/travis-fix into ** on master**. |
|
Changes Unknown when pulling 6ae8a48 on instification/travis-fix into ** on master**. |
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.
Travis tests are hanging. I can see from running
bin/createcoveragelocally that it opens the results in the browser. By outputting to the local directory the script exits and travis continues.I'm not sure if this is then going to affect how coverage.pickle2json and coveralls work - ie: are the results now going anywhere?