From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Elijah Newren" <newren@gmail.com>,
"Elijah Newren" <newren@gmail.com>
Subject: [PATCH] t4126: this test does not pass SANITIZE_LEAK; quit claiming it does
Date: Fri, 31 Dec 2021 05:15:02 +0000 [thread overview]
Message-ID: <pull.1177.git.git.1640927702745.gitgitgadget@gmail.com> (raw)
From: Elijah Newren <newren@gmail.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
---
t4126: this test does not pass SANITIZE_LEAK; quit claiming it does
My builds in several different topics keep running into this, and I'm
sure it's a false positive -- I didn't change anything affecting this
test. I've just been ignoring it and submitting anyway, and I suspect
others are too.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1177%2Fnewren%2Ft4126-apply-empty-is-not-leak-free-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1177/newren/t4126-apply-empty-is-not-leak-free-v1
Pull-Request: https://github.com/git/git/pull/1177
t/t4126-apply-empty.sh | 1 -
1 file changed, 1 deletion(-)
diff --git a/t/t4126-apply-empty.sh b/t/t4126-apply-empty.sh
index 82284d2f45d..ebbac79f20e 100755
--- a/t/t4126-apply-empty.sh
+++ b/t/t4126-apply-empty.sh
@@ -3,7 +3,6 @@
test_description='apply empty'
-TEST_PASSES_SANITIZE_LEAK=true
. ./test-lib.sh
test_expect_success setup '
base-commit: 2ae0a9cb8298185a94e5998086f380a355dd8907
--
gitgitgadget
next reply other threads:[~2021-12-31 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 5:15 Elijah Newren via GitGitGadget [this message]
2022-01-01 23:17 ` [PATCH] t4126: this test does not pass SANITIZE_LEAK; quit claiming it does Johannes Schindelin
2022-01-02 1:21 ` Junio C Hamano
2022-01-04 1:48 ` 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=pull.1177.git.git.1640927702745.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.