From: Eric Wong <normalperson@yhbt.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 4/4] t6000lib: workaround a possible dash bug
Date: Fri, 21 Sep 2007 13:45:11 -0700 [thread overview]
Message-ID: <20070921204511.GA10079@muzzle> (raw)
In-Reply-To: <20070921132808.GB9778@gondor.apana.org.au>
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Hi Eric:
Hi Herbert,
> On Thu, May 25, 2006 at 07:06:18PM -0700, Eric Wong wrote:
> > pdksh doesn't need this patch, of course bash works fine since
> > that what most users use.
> >
> > Normally, 'var=val command' seems to work fine with dash, but
> > perhaps there's something weird going on with "$@". dash is
> > pretty widespread, so it'll be good to support this even though
> > it does seem like a bug in dash.
>
> Just going through dash issues right now. Do you recall
> what the bug is in this case? Doing a quick test doesn't
> seem to show much:
>
> dash -c 'set -- env; a=b "$@"'
I tried to reproduce it on a quick script using shell functions,
multiple arguments, spaces in the $a variable.., but haven't
been successful. However, reverting the below patch still
causes errors in the latest git test suite.
> > diff --git a/t/t6000lib.sh b/t/t6000lib.sh
> > index c6752af..d402621 100755
> > --- a/t/t6000lib.sh
> > +++ b/t/t6000lib.sh
> > @@ -69,7 +69,9 @@ on_committer_date()
> > {
> > _date=$1
> > shift 1
> > - GIT_COMMITTER_DATE=$_date "$@"
> > + export GIT_COMMITTER_DATE="$_date"
> > + "$@"
> > + unset GIT_COMMITTER_DATE
> > }
> >
> > # Execute a command and suppress any error output.
> > --
> > 1.3.2.g7d11
>
> Thanks,
I'm using dash 0.5.3-7 from Debian Etch on x86-32.
(git @ 17ed158021ead9cb056f692fc35ff3fcde96a747)
*** t6003-rev-list-topo-order.sh ***
* ok 1: rev-list has correct number of entries
* ok 2: simple topo order
* ok 3: two diamonds topo order (g6)
* FAIL 4: multiple heads
check_output multiple-heads "git rev-list --topo-order a3 b3 c3"
* FAIL 5: multiple heads, prune at a1
check_output multiple-heads-prune-at-a1 "git rev-list --topo-order a3 b3 c3 ^a1"
* FAIL 6: multiple heads, prune at l1
check_output multiple-heads-prune-at-l1 "git rev-list --topo-order a3 b3 c3 ^l1"
* ok 7: cross-epoch, head at l5, prune at l1
* ok 8: duplicated head arguments
* ok 9: prune near topo
* ok 10: head has no parent
* ok 11: two nodes - one head, one base
* ok 12: three nodes one head, one internal, one base
* ok 13: linear prune l2 ^root
* ok 14: linear prune l2 ^l0
* ok 15: linear prune l2 ^l1
* ok 16: linear prune l5 ^a4
* ok 17: linear prune l5 ^l3
* ok 18: linear prune l5 ^l4
* ok 19: max-count 10 - topo order
* FAIL 20: max-count 10 - non topo order
check_output max-count-10-non-topo-order "git rev-list --max-count=10 l5"
* FAIL 21: --max-age=c3, no --topo-order
check_output max-age-c3-no-topo-order "git rev-list --max-age=1190407285 l5"
* ok 22: one specified head reachable from another a4, c3, --topo-order
* ok 23: one specified head reachable from another c3, a4, --topo-order
* ok 24: one specified head reachable from another a4, c3, no --topo-order
* ok 25: one specified head reachable from another c3, a4, no --topo-order
* ok 26: graph with c3 and a4 parents of head
* ok 27: graph with a4 and c3 parents of head
* ok 28: head ^head --topo-order
* ok 29: head ^head no --topo-order
* ok 30: simple topo order (l5r1)
* ok 31: simple topo order (r1l5)
* ok 32: don't print things unreachable from one branch
* ok 33: --topo-order a4 l3
* failed 5 among 33 test(s)
make: *** [t6003-rev-list-topo-order.sh] Error 1
--
Eric Wong
next prev parent reply other threads:[~2007-09-21 20:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 2:06 [PATCH 0/4] fix tests so they run without needing bash Eric Wong
2006-05-26 2:06 ` [PATCH 1/4] t3300-funny-names: shell portability fixes Eric Wong
2006-05-26 2:06 ` [PATCH 2/4] tests: Remove heredoc usage inside quotes Eric Wong
2006-05-26 2:06 ` [PATCH 3/4] t5500-fetch-pack: remove local (bashism) usage Eric Wong
2006-05-26 2:06 ` [PATCH 4/4] t6000lib: workaround a possible dash bug Eric Wong
2006-05-26 12:33 ` Herbert Xu
2007-09-21 13:28 ` Herbert Xu
2007-09-21 20:45 ` Eric Wong [this message]
2007-09-26 8:41 ` Herbert Xu
2006-05-26 12:23 ` [PATCH 3/4] t5500-fetch-pack: remove local (bashism) usage Herbert Xu
2006-05-29 5:28 ` Eric Wong
2006-05-29 5:36 ` Junio C Hamano
2006-05-29 7:31 ` Herbert Xu
2006-05-26 12:22 ` [PATCH 2/4] tests: Remove heredoc usage inside quotes Herbert Xu
2006-05-29 5:30 ` Eric Wong
2006-05-26 3:01 ` [PATCH 0/4] fix tests so they run without needing bash Junio C Hamano
2006-05-29 5:39 ` Eric Wong
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=20070921204511.GA10079@muzzle \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=junkio@cox.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.