From: Jeff King <peff@peff.net>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] t/perf: time rev-list with UNINTERESTING commits
Date: Mon, 20 Jan 2014 17:11:42 -0500 [thread overview]
Message-ID: <20140120221142.GA24320@sigill.intra.peff.net> (raw)
In-Reply-To: <20140120213101.GA16095@sigill.intra.peff.net>
On Mon, Jan 20, 2014 at 04:31:01PM -0500, Jeff King wrote:
> diff --git a/t/perf/p0001-rev-list.sh b/t/perf/p0001-rev-list.sh
> index 4f71a63..b7258a7 100755
> --- a/t/perf/p0001-rev-list.sh
> +++ b/t/perf/p0001-rev-list.sh
> @@ -14,4 +14,21 @@ test_perf 'rev-list --all --objects' '
> git rev-list --all --objects >/dev/null
> '
>
> +test_expect_success 'create new unreferenced commit' '
> + git checkout --detach HEAD &&
> + echo content >>file &&
> + git add file &&
> + git commit -m detached &&
> + commit=$(git rev-parse --verify HEAD) &&
> + git checkout -
> +'
This is bad to be touching the repo and assuming it is non-bare. For
some reason I assumed that the perf suite made a copy of the repo, but
it doesn't. If you point to a bare repo via GIT_PERF_REPO, this part of
the test fails.
It's actually enough to demonstrate the problem without changing the
tree at all. So this produces the same numbers, and works everywhere:
diff --git a/t/perf/p0001-rev-list.sh b/t/perf/p0001-rev-list.sh
index b7258a7..16359d5 100755
--- a/t/perf/p0001-rev-list.sh
+++ b/t/perf/p0001-rev-list.sh
@@ -15,12 +15,7 @@ test_perf 'rev-list --all --objects' '
'
test_expect_success 'create new unreferenced commit' '
- git checkout --detach HEAD &&
- echo content >>file &&
- git add file &&
- git commit -m detached &&
- commit=$(git rev-parse --verify HEAD) &&
- git checkout -
+ commit=$(git commit-tree HEAD^{tree} -p HEAD)
'
test_perf 'rev-list $commit --not --all' '
It still modifies the test repo, but at least in a fairly innocuous way.
-Peff
next prev parent reply other threads:[~2014-01-20 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 21:28 [PATCH 0/2] performance regression in mark_edges_uninteresting Jeff King
2014-01-20 21:31 ` [PATCH 1/2] t/perf: time rev-list with UNINTERESTING commits Jeff King
2014-01-20 22:11 ` Jeff King [this message]
2014-01-20 22:32 ` Thomas Rast
2014-01-20 22:39 ` Jeff King
2014-01-20 21:32 ` [PATCH 2/2] list-objects: only look at cmdline trees with edge_hint Jeff King
2014-01-20 23:57 ` Duy Nguyen
2014-01-21 2:22 ` Jeff King
2014-01-20 22:29 ` [PATCH 0/2] performance regression in mark_edges_uninteresting Jeff King
2014-01-21 2:24 ` [PATCH v2 " Jeff King
2014-01-21 2:25 ` [PATCH v2 1/2] t/perf: time rev-list with UNINTERESTING commits Jeff King
2014-01-21 2:25 ` [PATCH v2 2/2] list-objects: only look at cmdline trees with edge_hint Jeff King
2014-01-21 22:49 ` 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=20140120221142.GA24320@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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).