ci: run tests with SHA-256

Now that we have Git supporting SHA-256, we'd like to make sure that we
don't regress that state.  Unfortunately, it's easy to do so, so to
help, let's add code to run one of our CI jobs with SHA-256 as the
default hash.  This will help us detect any problems that may occur.

We pick the linux-clang job because it's relatively fast and the
linux-gcc job already runs the testsuite twice.  We want our tests to
run as fast as possible, so we wouldn't want to add a third run to the
linux-gcc job.  To make sure we properly exercise the code, let's run
the tests in the default mode (SHA-1) first and then run a second time
with SHA-256.  We explicitly specify SHA-1 for the first run so that if
we change the default in the future, we make sure to test both cases.

Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Reviewed-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

diff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh
index 17e25aade96f46ecfcdf1b5658d788f23b99f587..6c27b886b8f0cfb8d16a82318d884725a1ed607c 100755 (executable)
--- a/ci/run-build-and-tests.sh
+++ b/ci/run-build-and-tests.sh
@@ -24,6 +24,12 @@ linux-gcc)
        export GIT_TEST_ADD_I_USE_BUILTIN=1
        make test
        ;;
+linux-clang)
+       export GIT_TEST_DEFAULT_HASH=sha1
+       make test
+       export GIT_TEST_DEFAULT_HASH=sha256
+       make test
+       ;;
 linux-gcc-4.8)
        # Don't run the tests; we only care about whether Git can be
        # built with GCC 4.8, as it errors out on some undesired (C99)