From: "Torsten Bögershausen" <tboegi@web.de>
To: Jeff King <peff@peff.net>
Cc: John Szakmeister <john@szakmeister.net>,
Felipe Contreras <felipe.contreras@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: Build broken for contrib/remote-helpers...
Date: Tue, 22 Jan 2013 21:55:51 +0100 [thread overview]
Message-ID: <50FEFCD7.2060402@web.de> (raw)
In-Reply-To: <20130122194135.GA23521@sigill.intra.peff.net>
On 22.01.13 20:41, Jeff King wrote:
> On Tue, Jan 22, 2013 at 12:49:31AM -0500, John Szakmeister wrote:
>
>> I tried running make in contrib/remote-helpers and it died with:
>>
>> :: make
>> make -e -C ../../t test
>> rm -f -r test-results
>> duplicate test numbers: /Users/jszakmeister/sources/git
>> make[1]: *** [test-lint-duplicates] Error 1
>> make: *** [test] Error 2
>>
>> The path shown is not quite correct. I have the sources extracted to
>> /Users/jszakmeister/sources/git-1.8.1.1. It appears that the Makefile
>> in contrib/remote-helpers is exporting T, which is causing the
>> duplicate test detection to fail.
>
> It has to set T, because that is how t/Makefile knows what the set of
> tests is. The problem is that test-lint-duplicates does not understand
> absolute pathnames, as its regex is too simplistic:
>
> sed 's/-.*//' | sort | uniq -d
>
> So it finds whatever is before the first "-", which would be the test
> number in "t0000-basic.sh" or similar, and then looks for duplicates.
would it help to filter for numbered tests before sorting like this:
sed 's/-.*//' | grep "[0-9][0-9][0-9][0-9]"| sort | uniq -d
next prev parent reply other threads:[~2013-01-22 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 5:49 Build broken for contrib/remote-helpers John Szakmeister
2013-01-22 19:41 ` Jeff King
2013-01-22 20:55 ` Torsten Bögershausen [this message]
2013-01-22 22:22 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50FEFCD7.2060402@web.de \
--to=tboegi@web.de \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@szakmeister.net \
--cc=peff@peff.net \
/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.