From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git List <git@vger.kernel.org>
Subject: Re: &&-chaining tester
Date: Thu, 8 Dec 2011 01:06:36 +0530 [thread overview]
Message-ID: <1323286611-4806-1-git-send-email-artagnon@gmail.com> (raw)
In-Reply-To: <20111207100858.GB13374@elie.hsd1.il.comcast.net>
Hi,
Jonathan Nieder wrote:
> Ramkumar Ramachandra wrote:
>
>> Missing the chaining '&&' seems to be quite a common
>> error: I vaguely remember seeing a patch to detect this sometime ago.
>> Jonathan?
>
> [...]
> - fix all cases of broken &&-chaining. For extra bonus points,
> send out those patches, respond to reviews, and gently usher
> them into Junio's tree
Hm, involves a huge amount of janitorial work. Anyway, thanks for
pointing me in the right direction- here's a small start.
[What I used; for reference]
--
t/test-lib.sh | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/t/test-lib.sh b/t/test-lib.sh
index bdd9513..3bf75ac 100644
--- a/t/test-lib.sh
+++ b/t/test-lib.sh
@@ -472,7 +472,17 @@ test_eval_ () {
eval >&3 2>&4 "$*"
}
+check_command_chaining_ () {
+ eval >&3 2>&4 "(exit 189) && $1"
+ eval_chain_ret=$?
+ if test "$eval_chain_ret" != 189
+ then
+ echo '[CHAIN_BUG] in the test script: missing "&&" in test commands'
+ fi
+}
+
test_run_ () {
+ check_command_chaining_ "$1"
test_cleanup=:
expecting_failure=$2
test_eval_ "$1"
--
Thanks.
-- Ram
Ramkumar Ramachandra (15):
t1013 (loose-object-format): fix && chaining
t1300 (repo-config): fix && chaining
t1412 (reflog-loop): fix && chaining
t1007 (hash-object): fix && chaining
t1510 (repo-setup): fix && chaining
t1511 (rev-parse-caret): fix && chaining
t1510 (worktree): fix && chaining
t3200 (branch): fix && chaining
t3418 (rebase-continue): fix && chaining
t3400 (rebase): fix && chaining
t3310 (notes-merge-manual-resolve): fix && chaining
t3419 (rebase-patch-id): fix && chaining
t3030 (merge-recursive): use test_expect_code
t1006 (cat-file): use test_cmp
t3040 (subprojects-basic): modernize style
t/t1006-cat-file.sh | 53 +++---------
t/t1007-hash-object.sh | 16 ++--
t/t1013-loose-object-format.sh | 2 +-
t/t1300-repo-config.sh | 2 +-
t/t1412-reflog-loop.sh | 2 +-
t/t1501-worktree.sh | 6 +-
t/t1510-repo-setup.sh | 4 +-
t/t1511-rev-parse-caret.sh | 2 +-
t/t3030-merge-recursive.sh | 72 ++---------------
t/t3040-subprojects-basic.sh | 144 ++++++++++++++++----------------
t/t3200-branch.sh | 4 +-
t/t3310-notes-merge-manual-resolve.sh | 10 +-
t/t3400-rebase.sh | 4 +-
t/t3418-rebase-continue.sh | 4 +-
t/t3419-rebase-patch-id.sh | 2 +-
15 files changed, 119 insertions(+), 208 deletions(-)
--
1.7.7.3
next prev parent reply other threads:[~2011-12-07 19:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 5:01 What's cooking in git.git (Dec 2011, #02; Mon, 5) Junio C Hamano
2011-12-06 5:35 ` Ramkumar Ramachandra
2011-12-06 18:20 ` Junio C Hamano
2011-12-06 20:30 ` Ramkumar Ramachandra
2011-12-07 10:08 ` &&-chaining tester Jonathan Nieder
2011-12-07 19:36 ` Ramkumar Ramachandra [this message]
2011-12-07 19:36 ` [PATCH 01/15] t1013 (loose-object-format): fix && chaining Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 02/15] t1300 (repo-config): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 03/15] t1412 (reflog-loop): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 04/15] t1007 (hash-object): " Ramkumar Ramachandra
2011-12-07 21:47 ` Jonathan Nieder
2011-12-08 4:42 ` Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 05/15] t1510 (repo-setup): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 06/15] t1511 (rev-parse-caret): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 07/15] t1510 (worktree): " Ramkumar Ramachandra
2011-12-07 21:51 ` Jonathan Nieder
2011-12-08 4:39 ` Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 08/15] t3200 (branch): " Ramkumar Ramachandra
2011-12-07 21:55 ` Jonathan Nieder
2011-12-08 4:47 ` Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 09/15] t3418 (rebase-continue): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 10/15] t3400 (rebase): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 11/15] t3310 (notes-merge-manual-resolve): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 12/15] t3419 (rebase-patch-id): " Ramkumar Ramachandra
2011-12-07 19:36 ` [PATCH 13/15] t3030 (merge-recursive): use test_expect_code Ramkumar Ramachandra
2011-12-07 21:57 ` Jonathan Nieder
2011-12-07 19:36 ` [PATCH 14/15] t1006 (cat-file): use test_cmp Ramkumar Ramachandra
2011-12-07 22:01 ` Jonathan Nieder
2011-12-07 19:36 ` [PATCH 15/15] t3040 (subprojects-basic): modernize style Ramkumar Ramachandra
2011-12-07 22:21 ` Jonathan Nieder
2011-12-08 13:04 ` Ramkumar Ramachandra
2011-12-08 8:06 ` &&-chaining tester Matthieu Moy
2011-12-08 18:19 ` What's cooking in git.git (Dec 2011, #02; Mon, 5) Junio C Hamano
2011-12-06 5:52 ` Jeff King
2011-12-06 11:22 ` Erik Faye-Lund
2011-12-06 18:52 ` Jeff King
2011-12-08 19:44 ` Erik Faye-Lund
2011-12-08 21:25 ` Junio C Hamano
2011-12-06 18:35 ` Junio C Hamano
2011-12-06 18:47 ` Jeff King
2011-12-06 11:20 ` Nguyen Thai Ngoc Duy
2011-12-06 19:10 ` Junio C Hamano
2011-12-06 14:01 ` Nguyen Thai Ngoc Duy
2011-12-06 19:12 ` Junio C Hamano
2011-12-06 21:12 ` Luke Diamand
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=1323286611-4806-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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 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).