From: Eric Sunshine <sunshine@sunshineco.com>
To: Jeff King <peff@peff.net>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
"Karthik Nayak" <karthik.188@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: t6392 broken on pu (Mac OS X)
Date: Mon, 9 May 2016 12:30:43 -0400 [thread overview]
Message-ID: <CAPig+cQ2kSVzy0K303J3Guhk3-NzcReb5V7ohqOy2pPL_5GrSA@mail.gmail.com> (raw)
In-Reply-To: <20160509160725.GA11861@sigill.intra.peff.net>
On Mon, May 9, 2016 at 12:07 PM, Jeff King <peff@peff.net> wrote:
> On Sat, May 07, 2016 at 06:15:19PM +0200, Torsten Bögershausen wrote:
>> These tests fail here under Mac OS,
>> they pass under Linux:
>> commit ff3d9b660a4b6e9d3eeb664ce1febe717adff737
>> I haven't had a chance to dig further.
>
> I assume you mean t6302. It looks like the difference is not Mac OS, but
> rather that the GPG prerequisite is not fulfilled, so we are missing a
> few of the tags.
>
> Commit 618310a introduced a helper to munge the "expect" output. Using
> that fixes some of the cases, but not test 34. That one is expecting
> blank lines for tags, so test_prepare_expect doesn't know which lines
> are related to GPG.
>
> We could fix it by tweaking the test like this:
> [...snip...]
> However, I wonder if we could improve on the strategy in 618310a, and
> simply create non-signed versions of the "signed" tags when GPG is not
> available. That would make tests looking at the whole ref namespace
> more consistent. And any tests which wanted to look specifically at the
> signed attributes should be protected with the GPG prereq anyway (it
> doesn't look like there are any currently, though).
>
> I.e., something like:
> [...snip...]
> test_expect_success 'setup some history and refs' '
> @@ -24,9 +20,12 @@ test_expect_success 'setup some history and refs' '
> git tag -m "Annonated doubly" doubly-annotated-tag annotated-tag &&
> if test_have_prereq GPG
> then
> - git tag -s -m "A signed tag" signed-tag &&
> - git tag -s -m "Signed doubly" doubly-signed-tag signed-tag
> + sign=-s
> + else
> + sign=
> fi &&
> + git tag $sign -m "A signed tag" signed-tag &&
> + git tag $sign -m "Signed doubly" doubly-signed-tag signed-tag &&
> git checkout master &&
> git update-ref refs/odd/spot master
> '
The latter seems very preferable, though perhaps it could be made more
concise like this?
sign=
test_have_prereq GPG && sign=-s
(But that's a minor issue.)
next prev parent reply other threads:[~2016-05-09 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 16:15 t6392 broken on pu (Mac OS X) Torsten Bögershausen
2016-05-09 16:07 ` Jeff King
2016-05-09 16:30 ` Eric Sunshine [this message]
2016-05-09 16:49 ` [PATCH] t6302: simplify non-gpg cases Jeff King
2016-05-09 17:47 ` Eric Sunshine
[not found] ` <CAOLa=ZSZqs=++Hf8CF3pWEnJqmOA9ajuX03hzLMkuQ+ehXXCVQ@mail.gmail.com>
2016-05-09 21:37 ` Eric Sunshine
2016-05-10 2:40 ` [PATCH v2] " Jeff King
2016-05-10 2:49 ` Eric Sunshine
2016-05-10 6:03 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cQ2kSVzy0K303J3Guhk3-NzcReb5V7ohqOy2pPL_5GrSA@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=peff@peff.net \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).