diff options
| author | Todd Zullinger <tmz@pobox.com> | 2019-02-08 03:17:46 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2019-02-08 18:01:46 (GMT) |
| commit | 2e285e7803217c56f5e86a0abdec4b7fa8bc1058 (patch) | |
| tree | 1bd2b0a3c27eacca01546de2475a57767d8ac8f5 /t | |
| parent | ddf3a1152d32cc950389c9cb9e7b7962e7e14f16 (diff) | |
| download | git-2e285e7803217c56f5e86a0abdec4b7fa8bc1058.zip git-2e285e7803217c56f5e86a0abdec4b7fa8bc1058.tar.gz git-2e285e7803217c56f5e86a0abdec4b7fa8bc1058.tar.bz2 | |
t/lib-gpg: drop redundant killing of gpg-agent
In 53fc999306 ("gpg-interface t: extend the existing GPG tests with
GPGSM", 2018-07-20), the gpgconf call which kills gpg-agent was copied
from the existing gpg setup code.
The reason for killing gpg-agent is given in 29ff1f8f74 ("t: lib-gpg:
flush gpg agent on startup", 2017-07-20):
When running gpg-relevant tests, a gpg-daemon is spawned for each
GNUPGHOME used. This daemon may stay running after the test and cache
file descriptors for the trash directories, even after the trash
directory is removed. This leads to ENOENT errors when attempting to
create files if tests are run multiple times.
Add a cleanup script to force flushing the gpg-agent for that GNUPGHOME
(if any) before setting up the GPG relevant-environment.
Killing gpg-agent once per test is sufficient.
Signed-off-by: Todd Zullinger <tmz@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't')
| -rwxr-xr-x | t/lib-gpg.sh | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/t/lib-gpg.sh b/t/lib-gpg.sh index d90160e..041f101 100755 --- a/t/lib-gpg.sh +++ b/t/lib-gpg.sh @@ -61,7 +61,6 @@ then | grep fingerprint: | cut -d" " -f4 | tr -d '\n' > \ ${GNUPGHOME}/trustlist.txt && echo " S relax" >>"${GNUPGHOME}/trustlist.txt" && - (gpgconf --kill gpg-agent >/dev/null 2>&1 || : ) && echo hello | gpgsm --homedir "${GNUPGHOME}" >/dev/null \ -u committer@example.com -o /dev/null --sign - 2>&1 && test_set_prereq GPGSM |