avoid setEnv while testing gpg
setEnv is not thread safe and could cause a getEnv by another thread to segfault, or perhaps other had behavior. Sponsored-by: Dartmouth College's Datalad project
This commit is contained in:
parent
4ba7a97d8c
commit
ebb76f0486
5 changed files with 89 additions and 75 deletions
|
@ -18,3 +18,5 @@ toplevel MVar would be ok, since tests don't run concurrently?
|
|||
There is also Utility.Gpg.testHarness, which sets GNUPGHOME. It seems that
|
||||
instead, every place that git-annex is run inside the gpg test harness
|
||||
would need to add GNUPGHOME to the environment of the git-annex process.
|
||||
|
||||
> Fixed this part to not setEnv. --[[Joey]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue