From: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: vdye@github.com, gitster@pobox.com,
Derrick Stolee <derrickstolee@github.com>,
Derrick Stolee <derrickstolee@github.com>
Subject: [PATCH 1/3] t: allow 'scalar' in test_must_fail
Date: Fri, 27 Jan 2023 20:06:01 +0000 [thread overview]
Message-ID: <94630bc3bc7f4f236c28e791e0faba6590c735e8.1674849963.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1473.git.1674849963.gitgitgadget@gmail.com>
From: Derrick Stolee <derrickstolee@github.com>
This will enable scalar tests to use the test_must_fail helper, when
necessary.
Signed-off-by: Derrick Stolee <derrickstolee@github.com>
---
t/test-lib-functions.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index 79922227030..75b8ee95e7f 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -1016,7 +1016,7 @@ test_must_fail_acceptable () {
fi
case "$1" in
- git|__git*|test-tool|test_terminal)
+ git|__git*|scalar|test-tool|test_terminal)
return 0
;;
*)
--
gitgitgadget
next prev parent reply other threads:[~2023-01-27 20:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 20:06 [PATCH 0/3] Allow scalar to succeed despite maintenance failures Derrick Stolee via GitGitGadget
2023-01-27 20:06 ` Derrick Stolee via GitGitGadget [this message]
2023-01-27 20:06 ` [PATCH 2/3] t921*: test scalar behavior starting maintenance Derrick Stolee via GitGitGadget
2023-01-27 20:06 ` [PATCH 3/3] scalar: only warn when background maintenance fails Derrick Stolee via GitGitGadget
2023-01-27 20:36 ` Junio C Hamano
2023-01-27 22:18 ` Derrick Stolee
2023-01-28 0:32 ` Junio C Hamano
2023-01-30 13:44 ` Derrick Stolee
2023-01-30 15:40 ` Junio C Hamano
2023-01-30 17:42 ` Victoria Dye
2023-01-30 18:58 ` Junio C Hamano
2023-01-30 19:06 ` Derrick Stolee
2023-01-27 22:18 ` Victoria Dye
2023-01-30 19:25 ` Derrick Stolee
2023-01-27 22:06 ` Victoria Dye
2023-01-27 22:14 ` Derrick Stolee
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=94630bc3bc7f4f236c28e791e0faba6590c735e8.1674849963.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vdye@github.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 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).