Fix test_VerifySignature on devel #64
Merged
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
|
Can one of the admins verify this patch? |
1 similar comment
|
Can one of the admins verify this patch? |
mdellweg
approved these changes
Jan 16, 2019
|
A riddle, wrapped in a mystery. Thanks! |
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.
The
test_VerifySignaturetest will not run on mydevel_pulp2_devVagrant box without this line.Instead it throws a
raise Exception("No GPG-keys in keyring, did the import fail?").Since Travis appears to be doing fine without this fix, it would be good to know if others are having the same problem, or what the difference between Travis and my local Vagrant box is...
Edit: I added a pulp.plan.io issue to go with this PR:
https://pulp.plan.io/issues/4332