From: Junio C Hamano <gitster@pobox.com>
To: Theodore Ts'o <tytso@mit.edu>, Andi Kleen <ak@linux.intel.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.1.0
Date: Sun, 17 Aug 2014 12:19:21 -0700 [thread overview]
Message-ID: <xmqq38cuzzye.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140815231822.GM10808@thunk.org> (Theodore Ts'o's message of "Fri, 15 Aug 2014 19:18:22 -0400")
Theodore Ts'o <tytso@mit.edu> writes:
> On Fri, Aug 15, 2014 at 03:46:29PM -0700, Junio C Hamano wrote:
>> The latest feature release Git v2.1.0 is now available at the
>> usual places.
>
> I pulled down git v2.1.0, and when I tried to build it via:
>
> make prefix=/usr/local profile-fast
>
> The build died with this:
>
> cannot open test-results/p5302-pack-index.subtests: No such file or directory at ./aggregate.perl line 77.
> Makefile:7: recipe for target 'perf' failed
> make[2]: *** [perf] Error 2
> make[2]: Leaving directory '/usr/projects/git/git/t/perf'
>
> Not a big deal, but I thought I would mention it.
Thanks.
But this does not seem to reproduce for me (note: I never build
profile-anything myself so I may not be seeing the error even there
is---the only thing I checked was the lack of make errors).
We did have changes to profile-feedback build during this round:
$ git shortlog 3b3b61c^..3b3b61c^2
Andi Kleen (4):
Use BASIC_FLAGS for profile feedback
Don't define away __attribute__ on gcc
Run the perf test suite for profile feedback too
Fix profile feedback with -jN and add profile-fast
I admit I didn't try -jN, and if there are leaky dependencies in the
last patch, it may explain the symptom.
next prev parent reply other threads:[~2014-08-17 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 22:46 [ANNOUNCE] Git v2.1.0 Junio C Hamano
2014-08-15 23:18 ` Theodore Ts'o
2014-08-17 19:19 ` Junio C Hamano [this message]
2014-08-17 14:10 ` Ramsay Jones
2014-08-17 19:25 ` 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=xmqq38cuzzye.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=ak@linux.intel.com \
--cc=git@vger.kernel.org \
--cc=tytso@mit.edu \
/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.