From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: paul@mad-scientist.net, git@vger.kernel.org
Subject: Re: profile-fast is failing in my Git 2.2.1 build from tar in a Git repo
Date: Mon, 12 Jan 2015 16:16:05 -0500 [thread overview]
Message-ID: <20150112211604.GB10409@peff.net> (raw)
In-Reply-To: <20150112210827.GA10409@peff.net>
On Mon, Jan 12, 2015 at 04:08:28PM -0500, Jeff King wrote:
> > I do not think profile build is prepared to be run without having
> > our history (after all, it is not test_perf_create_REPO_from, not
> > test_perf_create_source_directory_of_git_from). It wants to create
> > a repository that hosts a reasonably sized but not too big a
> > project, i.e. us.
> >
> > The safest and cleanest fix would be to make sure that the said
> > function checks if $source/.git is a repository, perhaps?
>
> Hmph. We already dealt with this once in 93b5393 (Makefile: make perf
> tests optional for profile build, 2014-08-19). That check explicitly
> looks for ".git" (and not checking that we are in an outer git repo), so
> I am not sure why it is kicking in at all. But probably the fix should
> go there.
Oh, I see. It is because Paul is using profile-fast, which does not have
that check. And I did not add it as part of 93b5393, because it would
not make sense. If you do not do the perf tests, then profile-fast is
literally doing nothing. :)
I think the right solution is either:
1. Switch to using "make profile", which will use the regular test
suite to gather data, and skip the perf tests.
2. Set GIT_PERF_REPO to some representative repo of your choice for
gathering profiling data (it does not have to be git.git at all,
but it is probably more useful if it is not a tiny toy repo).
We _could_ teach the perf code to look upwards for a surrounding repo
with `git rev-parse` rather than looking for ../../.git. But there is no
guarantee that the repo we find would actually be a useful one for doing
perf tests. I'd just as soon leave it as-is, and have people specify a
useful repo via GIT_PERF_REPO if they have one.
-Peff
prev parent reply other threads:[~2015-01-12 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 21:58 profile-fast is failing in my Git 2.2.1 build from tar in a Git repo Paul Smith
2015-01-06 23:13 ` Junio C Hamano
2015-01-12 21:08 ` Jeff King
2015-01-12 21:16 ` Jeff King [this message]
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=20150112211604.GB10409@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paul@mad-scientist.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).