Fix user and repo tests for Travis #358
Merged
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
Not sure of the exact date, but Travis is no longer case-sensitive when dealing with user and repo names, at least as of the date of this commit. Since these are the only tests in `local` we have for checking if a repo exists in Travis, I've added a random hex-string to the end the repo and user, respectively, to ensure that the `RuntimeError` is raised as expected.
Member
|
Oh OK. I thought the test failures had to do with the fork changes, but I guess those are just in the tests for #343. |
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.
Not sure of the exact date, but Travis is no longer case-sensitive when
dealing with user and repo names, at least as of the date of this
commit.
Since these are the only tests in
localwe have for checking if a repoexists in Travis, I've added a random hex-string to the end the repo and
user, respectively, to ensure that the
RuntimeErroris raised asexpected.