summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2025-11-04 07:48:09 -0800
committerJunio C Hamano <gitster@pobox.com>2025-11-04 07:48:09 -0800
commit55e8615d1845aeb5e2276c9cee87ef141f9c7447 (patch)
tree344dc77f65f195d15e3dd0b6b6ead3639e4e0ea4
parentMerge branch 'kh/doc-checkout-markup-fix' (diff)
parentt1016-compatObjectFormat: really freeze time for reproduciblity (diff)
downloadgit-55e8615d1845aeb5e2276c9cee87ef141f9c7447.tar.gz
git-55e8615d1845aeb5e2276c9cee87ef141f9c7447.zip
Merge branch 'eb/t1016-hash-transition-fix'
Test fix. * eb/t1016-hash-transition-fix: t1016-compatObjectFormat: really freeze time for reproduciblity
-rwxr-xr-xt/t1016-compatObjectFormat.sh6
-rwxr-xr-xt/t1016/gpg2
2 files changed, 7 insertions, 1 deletions
diff --git a/t/t1016-compatObjectFormat.sh b/t/t1016-compatObjectFormat.sh
index a9af8b2396..0efce53f3a 100755
--- a/t/t1016-compatObjectFormat.sh
+++ b/t/t1016-compatObjectFormat.sh
@@ -21,6 +21,12 @@ test_description='Test how well compatObjectFormat works'
# different hash functions result in the same content in the commits.
# This means that when the commit is translated between hash functions
# the commit is identical to the commit in the other repository.
+#
+# Similarly this test relies on:
+# gpg --faked-system-time '20230918T154812!
+# freezing the system time from gpg perspective so that two different
+# runs of gpg applied to the same data result in identical signatures.
+#
compat_hash () {
case "$1" in
diff --git a/t/t1016/gpg b/t/t1016/gpg
index 2601cb18a5..34d6e055fc 100755
--- a/t/t1016/gpg
+++ b/t/t1016/gpg
@@ -1,2 +1,2 @@
#!/bin/sh
-exec gpg --faked-system-time "20230918T154812" "$@"
+exec gpg --faked-system-time '20230918T154812!' "$@"