Avoid a test suite failure when the environment does not let gpg be tested
Due to eg, too long a path to the agent socket, caused by running gpg in a container where /run is not mounted, and/or some other gpg behavior like unnecessarily making relative paths to its home directory absolute.
This commit is contained in:
parent
24eabbbc55
commit
4a6d328ae9
5 changed files with 42 additions and 13 deletions
|
@ -41,3 +41,5 @@ FWIW,
|
|||
|
||||
[[!meta author=yoh]]
|
||||
[[!tag projects/datalad]]
|
||||
|
||||
> [[fixed|done]] --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,11 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 6"""
|
||||
date="2020-04-28T19:29:05Z"
|
||||
content="""
|
||||
Hmm, it could be that /run is not mounted in the container and then gpg
|
||||
falls back to putting the socket in the home directory.
|
||||
|
||||
Ok, I'm just going to make this test be skipped if it fails to import the
|
||||
test key.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue