On Tue, Apr 06, 2021 at 06:35:57PM +0800, ZheNing Hu wrote:
> ZheNing Hu <adlternative@xxxxxxxxx> 于2021年4月6日周二 下午5:49写道：
> > But this is the first time I use `t/perf/*` and there is a little problem.
> > It seem like whatever I run single script like `sh ./p0007-write-cache.sh`
> > or just `make` or `./run ${HOME}/git -- ./p0002-read-cache.sh` , these
> > tests will fail.
> >
> It's because I don't have /usr/bin/time, solved after installation.
> So best have this:
>
> --- a/t/perf/perf-lib.sh
> +++ b/t/perf/perf-lib.sh
> @@ -152,6 +152,10 @@ immediate=t
> # Perf tests require GNU time
> case "$(uname -s)" in Darwin) GTIME="${GTIME:-gtime}";; esac
> GTIME="${GTIME:-/usr/bin/time}"
> +if ! test -f "$GTIME"
> +then
> + error "command not found: "$GTIME""
> +fi
This patch would create problems when we expect to find the value of
$GTIME in the $PATH e.g., you can see in the Darwin case it is set to
just "gtime", not an absolute path).
I am sympathetic to helping people see what's wrong, but I think in this
case we're better off pointing people to using "-v". E.g.:
$ GTIME=pretend-we-do-not-have-gtime ./p0001-rev-list.sh
perf 1 - rev-list --all:
not ok 1 - rev-list --all
#
# git rev-list --all >/dev/null
#
Uh oh, that wasn't very informative. But how about this:
$ GTIME=pretend-we-do-not-have-gtime ./p0001-rev-list.sh -v
[...]
perf 1 - rev-list --all:
running:
git rev-list --all >/dev/null
./p0001-rev-list.sh: 160: pretend-we-do-not-have-gtime: not found
not ok 1 - rev-list --all
#
# git rev-list --all >/dev/null
#
which I think makes it reasonably clear.
-Peff
