From: Jeff King <peff@peff.net>
To: Luke Diamand <luke@diamand.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] git-p4: prevent --chain-lint failure
Date: Mon, 27 Apr 2015 19:02:23 -0400 [thread overview]
Message-ID: <20150427230223.GA22403@peff.net> (raw)
In-Reply-To: <1430173228-22004-2-git-send-email-luke@diamand.org>
On Mon, Apr 27, 2015 at 11:20:28PM +0100, Luke Diamand wrote:
> t9814 has a test that simply sets up a pre-requisite for
> another test, and as such, always succeeds. The way it was
> written doesn't quite work with the test lint checks introduced
> with the --chain-lint option.
>
> Add an additional layer of {} to prevent the --chain-lint
> code getting confused.
Thanks for looking into this. I tried to fix any existing tests I could,
but I missed ones whose prerequisites aren't met on my system.
Using {} is reasonable in general; that's how the fixes in 9ddc5ac (t:
wrap complicated expect_code users in a block, 2015-03-20) worked.
However, I think your case is somewhat simpler, in that you really just
want a big conditional to set a prereq based on whether or not a command
succeeds.
Would it make sense to convert this whole thing to just:
test_lazy_prereq P4D_HAVE_CONFIGURABLE_RUN_MOVE_ALLOW '
p4 configure show run.move.allow >out &&
egrep ^run.move.allow: out
'
?
-Peff
next prev parent reply other threads:[~2015-04-27 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 22:20 [PATCH] Fixup test-lint error in git-p4 t9814 test Luke Diamand
2015-04-27 22:20 ` [PATCH] git-p4: prevent --chain-lint failure Luke Diamand
2015-04-27 23:02 ` Jeff King [this message]
2015-04-28 6:30 ` [PATCHv2] Fixup test-lint error in git-p4 t9814 test Luke Diamand
2015-04-28 7:21 ` [PATCHv3] " Luke Diamand
2015-04-28 7:21 ` [PATCHv3] git-p4: t9814: prevent --chain-lint failure Luke Diamand
2015-04-28 6:30 ` [PATCHv2] " 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=20150427230223.GA22403@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luke@diamand.org \
/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.