From: Jeff King <peff@peff.net>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] test suite: add a check that all test numbers are unique
Date: Fri, 21 Aug 2009 08:53:24 -0400 [thread overview]
Message-ID: <20090821125324.GA6280@coredump.intra.peff.net> (raw)
In-Reply-To: <4A8E68AF.8040001@viscovery.net>
On Fri, Aug 21, 2009 at 11:28:15AM +0200, Johannes Sixt wrote:
> The test runs only if 'make all' is used. Its purpose is to alert our
> valued integrator if different branches are merged that happen to
> introduce the same test number.
I think this is probably useful. In addition to the t7406 you posted a
patch for, it looks like t4037 has a duplicate in next.
As for the implementation:
> +++ b/t/check_unique_numbers.sh
> @@ -0,0 +1,27 @@
> +#!/bin/sh
> +
> +# checks whether test case numbers are unique;
> +# returns non-zero if any duplicates were found
> +
> +check_numbers () {
> + last= dup=
> + while read name
> + do
> + case $name in
> + t[0-9][0-9][0-9][0-9]-*.sh)
> + number=${name%%-*}
> + if test "$number" = "$last"; then
> + dup="$dup $number"
> + fi
> + last=$number
> + ;;
> + esac
> + done
> + test -z "$dup" || {
> + echo >&2 "error: duplicate test numbers:" $dup
> + return 1
> + }
> +}
> +
> +ls -1 | # no wildcard to avoid overflow of command line
> +check_numbers
Why not the much shorter:
tests() {
ls | sed -n 's/^\(t[0-9][0-9][0-9][0-9]\)-.*\.sh$/\1/p'
}
dups=`tests | uniq -d`
instead of the long shell loop?
-Peff
next prev parent reply other threads:[~2009-08-21 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 9:28 [PATCH] test suite: add a check that all test numbers are unique Johannes Sixt
2009-08-21 12:53 ` Jeff King [this message]
2009-08-21 13:13 ` [PATCH v2] " Johannes Sixt
2009-08-21 14:37 ` Jeff King
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=20090821125324.GA6280@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.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 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).