From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Elijah Newren" <newren@gmail.com>,
"Martin Ågren" <martin.agren@gmail.com>,
"Andrzej Hunt" <ajrhunt@google.com>, "Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH 14/15] leak tests: mark some config tests as passing with SANITIZE=leak
Date: Sun, 31 Oct 2021 00:24:23 +0200 [thread overview]
Message-ID: <patch-14.15-9902e353dda-20211030T221945Z-avarab@gmail.com> (raw)
In-Reply-To: <cover-00.15-00000000000-20211030T221945Z-avarab@gmail.com>
Mark some tests that match "*config*" as passing when git is compiled
with SANITIZE=leak. They'll now be listed as running under the
"GIT_TEST_PASSING_SANITIZE_LEAK=true" test mode (the "linux-leaks" CI
target).
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
---
t/t1300-config.sh | 1 +
t/t1303-wacky-config.sh | 2 ++
t/t1307-config-blob.sh | 2 ++
t/t1308-config-set.sh | 1 +
t/t1309-early-config.sh | 1 +
t/t1310-config-default.sh | 1 +
t/t2404-worktree-config.sh | 1 +
7 files changed, 9 insertions(+)
diff --git a/t/t1300-config.sh b/t/t1300-config.sh
index 9ff46f3b047..f8031afaaf9 100755
--- a/t/t1300-config.sh
+++ b/t/t1300-config.sh
@@ -8,6 +8,7 @@ test_description='Test git config in different settings'
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=main
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME
+TEST_PASSES_SANITIZE_LEAK=true
. ./test-lib.sh
test_expect_success 'clear default config' '
diff --git a/t/t1303-wacky-config.sh b/t/t1303-wacky-config.sh
index 0000e664e7b..0506f3d6bba 100755
--- a/t/t1303-wacky-config.sh
+++ b/t/t1303-wacky-config.sh
@@ -1,6 +1,8 @@
#!/bin/sh
test_description='Test wacky input to git config'
+
+TEST_PASSES_SANITIZE_LEAK=true
. ./test-lib.sh
# Leaving off the newline is intentional!
diff --git a/t/t1307-config-blob.sh b/t/t1307-config-blob.sh
index 930dce06f0f..0a7099d6f52 100755
--- a/t/t1307-config-blob.sh
+++ b/t/t1307-config-blob.sh
@@ -1,6 +1,8 @@
#!/bin/sh
test_description='support for reading config from a blob'
+
+TEST_PASSES_SANITIZE_LEAK=true
. ./test-lib.sh
test_expect_success 'create config blob' '
diff --git a/t/t1308-config-set.sh b/t/t1308-config-set.sh
index 88b119a0a35..b38e158d3b2 100755
--- a/t/t1308-config-set.sh
+++ b/t/t1308-config-set.sh
@@ -2,6 +2,7 @@
test_description='Test git config-set API in different settings'
+TEST_PASSES_SANITIZE_LEAK=true
. ./test-lib.sh
# 'check_config get_* section.key value' verifies that the entry for
diff --git a/t/t1309-early-config.sh b/t/t1309-early-config.sh
index b4a9158307f..537435b90ae 100755
--- a/t/t1309-early-config.sh
+++ b/t/t1309-early-config.sh
@@ -2,6 +2,7 @@
test_description='Test read_early_config()'
+TEST_PASSES_SANITIZE_LEAK=true
. ./test-lib.sh
test_expect_success 'read early config' '
diff --git a/t/t1310-config-default.sh b/t/t1310-config-default.sh
index 6049d917081..09b10c144ba 100755
--- a/t/t1310-config-default.sh
+++ b/t/t1310-config-default.sh
@@ -2,6 +2,7 @@
test_description='Test git config in different settings (with --default)'
+TEST_PASSES_SANITIZE_LEAK=true
. ./test-lib.sh
test_expect_success 'uses --default when entry missing' '
diff --git a/t/t2404-worktree-config.sh b/t/t2404-worktree-config.sh
index 9536d109195..842937bfb9a 100755
--- a/t/t2404-worktree-config.sh
+++ b/t/t2404-worktree-config.sh
@@ -2,6 +2,7 @@
test_description="config file in multi worktree"
+TEST_PASSES_SANITIZE_LEAK=true
. ./test-lib.sh
test_expect_success 'setup' '
--
2.33.1.1570.g069344fdd45
next prev parent reply other threads:[~2021-10-30 22:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 22:24 [PATCH 00/15] leak tests: remaining non-svn non-p4 tests as passing Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 01/15] leak tests: mark a read-tree test as passing SANITIZE=leak Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 02/15] leak tests: mark "sort" " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 03/15] leak tests: mark most gettext tests as passing with SANITIZE=leak Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 04/15] leak tests: mark some misc " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 05/15] leak tests: mark some rev-list " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 06/15] leak tests: mark some rev-parse " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 07/15] leak tests: mark some update-index " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 08/15] leak tests: mark some notes " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 09/15] leak tests: mark some apply " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 10/15] leak tests: mark some diff " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 11/15] leak tests: mark some add " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 12/15] leak tests: mark some clone " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` [PATCH 13/15] leak tests: mark some status " Ævar Arnfjörð Bjarmason
2021-10-30 22:24 ` Ævar Arnfjörð Bjarmason [this message]
2021-10-30 22:24 ` [PATCH 15/15] leak tests: mark some fast-import " Ævar Arnfjörð Bjarmason
2021-11-15 22:14 ` [PATCH 00/15] leak tests: remaining non-svn non-p4 tests as passing Elijah Newren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=patch-14.15-9902e353dda-20211030T221945Z-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=ajrhunt@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.agren@gmail.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).