From: Junio C Hamano <gitster@pobox.com>
To: paul@mad-scientist.net
Cc: git@vger.kernel.org
Subject: Re: profile-fast is failing in my Git 2.2.1 build from tar in a Git repo
Date: Tue, 06 Jan 2015 15:13:30 -0800 [thread overview]
Message-ID: <xmqq1tn7o63p.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1420408723.7095.207.camel@homebase> (Paul Smith's message of "Sun, 04 Jan 2015 16:58:43 -0500")
Paul Smith <paul@mad-scientist.net> writes:
> Is anyone aware of this? It seems that profile-fast fails when invoked
> from a downloaded tarball, if you are in a Git repository when you
> unpack it.
Not me (I don't do profile build), but I am not surprised.
> The problem is in the t/perf/perf-lib.sh:test_perf_create_repo_from()
> function, where we see this:
>
> repo="$1"
> source="$2"
> source_git=$source/$(cd "$source" && git rev-parse --git-dir)
>
> The function is invoked as:
>
> test_perf_create_repo_from '/home/psmith/src/git-2.2.1/t/perf/trash
> directory.p5302-pack-index' /home/psmith/src/git-2.2.1/t/..
>
> but this doesn't work, because "$source" is not a Git repository; it's
> the root of the unpacked tarball.
Yup, that is exactly why I said I am not surprised.
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?
next prev parent reply other threads:[~2015-01-06 23:13 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 [this message]
2015-01-12 21:08 ` Jeff King
2015-01-12 21:16 ` 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=xmqq1tn7o63p.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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 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.