From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.1 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CC950C433F7 for ; Mon, 13 Jul 2020 02:49:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9F9972070B for ; Mon, 13 Jul 2020 02:49:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (3072-bit key) header.d=crustytoothpaste.net header.i=@crustytoothpaste.net header.b="XgPmS/b5" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728633AbgGMCtq (ORCPT ); Sun, 12 Jul 2020 22:49:46 -0400 Received: from injection.crustytoothpaste.net ([192.241.140.119]:40618 "EHLO injection.crustytoothpaste.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728404AbgGMCtp (ORCPT ); Sun, 12 Jul 2020 22:49:45 -0400 Received: from camp.crustytoothpaste.net (unknown [IPv6:2001:470:b978:101:b610:a2f0:36c1:12e3]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by injection.crustytoothpaste.net (Postfix) with ESMTPSA id 52FE060A79; Mon, 13 Jul 2020 02:49:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crustytoothpaste.net; s=default; t=1594608581; bh=RZkf13Z5+0o7/YS0PxOH8OIwQKOadGhIo4GvGuDnDCY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From:Reply-To: Subject:Date:To:CC:Resent-Date:Resent-From:Resent-To:Resent-Cc: In-Reply-To:References:Content-Type:Content-Disposition; b=XgPmS/b5f39NM6vR1++ix52TTvYsq89eU+soHw5QTRyfhUSMagUODQYcMEvVyJu4G MOUIkn2SKnBgltoii6vX0twLY/k7HzV3S1s6Sfjt1T9LIpnvTLzTLCqYO34p5484y1 ryOwviS+GrE/ILiACLMwlcZETXU6SjarWC8DRC1fS97F7fhHNJ7JNpAgPlkZdT8hhS aV3HO7Mo/ERpuXSChXPjZUkAsZ+D1unOJXajFRHfXAT2CrtEKCtbH/0b8EzREmFKM/ Yvr5Mjjvf/SPA2QDLbxIygJgwZjSpSkvj5jIJlwXZgfEBkuTi9igIUmT+U8rx4QCww fhasBWNZo0L4+dyhhO+Q4vqSegxcZo/51bE94+RYyMkYljMo4frLDW5kM+RwL0RgOy Sqnou63CLsRntjkz/6ru02s2+SuHZvaoO9nlXjNsjW7dPoZUeVuuaLHp9BehzIf4F7 NurVaDrGOm8Ow1xrQfIeFk5lp5v1dkpkCIbiWjvVCSyFwmjfWcU From: "brian m. carlson" To: Cc: Denton Liu , Derrick Stolee Subject: [PATCH v2 37/39] ci: run tests with SHA-256 Date: Mon, 13 Jul 2020 02:49:07 +0000 Message-Id: <20200713024909.3714837-38-sandals@crustytoothpaste.net> X-Mailer: git-send-email 2.27.0.353.gb9a2d1a020 In-Reply-To: <20200713024909.3714837-1-sandals@crustytoothpaste.net> References: <20200713024909.3714837-1-sandals@crustytoothpaste.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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. Signed-off-by: brian m. carlson --- ci/run-build-and-tests.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh index 17e25aade9..a1a6a28791 100755 --- a/ci/run-build-and-tests.sh +++ b/ci/run-build-and-tests.sh @@ -24,6 +24,11 @@ linux-gcc) export GIT_TEST_ADD_I_USE_BUILTIN=1 make test ;; +linux-clang) + 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)