git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeremy Huddleston Sequoia <jeremyhu@freedesktop.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: git 2.10.1 test regression in t4014-format-patch.sh
Date: Sun, 9 Oct 2016 19:55:26 -0700	[thread overview]
Message-ID: <DEE09909-A5C9-47D8-B71E-0EC0D6C11B3D@freedesktop.org> (raw)
In-Reply-To: <F069D0FD-C3CF-4F40-9338-D84E76DB310B@joshtriplett.org>

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]


> On Oct 9, 2016, at 17:18, Josh Triplett <josh@joshtriplett.org> wrote:
> 
> On October 9, 2016 5:15:22 PM PDT, Jeremy Huddleston Sequoia <jeremyhu@freedesktop.org> wrote:
>> Hey Josh,
>> 
>> Hope you're doing well.
>> 
>> I wanted to let you know that this patch of yours, which landed in git
>> 2.10.1, introduced some test failures, seen on macOS.
>> 
>> Let me know if you need any additional information to track these down.
>> 
>> Thanks,
>> Jeremy
>> 
>> 
>> not ok 65 - format-patch default signature
>> #	
>> #		git format-patch --stdout -1 | tail -n 3 >output &&
>> #		signature >expect &&
>> #		test_cmp expect output
>> #	
>> 
>> not ok 132 - format-patch --base
>> #	
>> #		git checkout side &&
>> #		git format-patch --stdout --base=HEAD~3 -1 | tail -n 7 >actual &&
>> #		echo >expected &&
>> #		echo "base-commit: $(git rev-parse HEAD~3)" >>expected &&
>> #		echo "prerequisite-patch-id: $(git show --patch HEAD~2 | git
>> patch-id --stable | awk "{print \$1}")" >>expected &&
>> #		echo "prerequisite-patch-id: $(git show --patch HEAD~1 | git
>> patch-id --stable | awk "{print \$1}")" >>expected &&
>> #		signature >> expected &&
>> #		test_cmp expected actual
>> #	
> 
> Can you run the test with the option to show the expected and actual strings?
> Did the testsuite run with the wrong git somehow?

Nope, it's the right version being tested.  The failure seems due to your git_version change not liking our formatting

$ git --version
git version 2.10.1 (Apple Git-99)

(the 'Apple Git-XX' being added because this was from a build that had Apple's patch series, including https://github.com/jeremyhu/git/commit/f99905d0752d923e5ec61e14c675a300c6d04284)

We modify DEF_VER, which confused your regex.  Simple patch inc in a separate email.

Thanks,
Jeremy


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4465 bytes --]

      reply	other threads:[~2016-10-10  2:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10  0:15 git 2.10.1 test regression in t4014-format-patch.sh Jeremy Huddleston Sequoia
2016-10-10  0:18 ` Josh Triplett
2016-10-10  2:55   ` Jeremy Huddleston Sequoia [this message]

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=DEE09909-A5C9-47D8-B71E-0EC0D6C11B3D@freedesktop.org \
    --to=jeremyhu@freedesktop.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=josh@joshtriplett.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.
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).