Re: Built Git 2.27.0 from sources on macOS Catalina fails on "make profile"

From: Fabio Frumento <frumento.fabio@gmail.com>
Date: Jul 1, 2020, 16:14 UTC
Message-ID: <C72555F0-4CAE-4488-B32E-FD06D1204935@gmail.com>
In-Reply-To: <20200701161018.GD6726@coredump.intra.peff.net>

You got it!

++ test_must_be_empty err ++ test_path_is_file err ++ test -f err ++ test -s err ++ echo ''\''err'\'' is not empty, it contains:' 'err' is not empty, it contains: ++ cat err LLVM Profile Warning: Unable to track new values: Running out of static counters. Consider using option -mllvm -vp-counters-per-site=<n> to allocate more value profile counters at compile time. LLVM Profile Warning: Unable to track new values: Running out of static counters. Consider using option -mllvm -vp-counters-per-site=<n> to allocate more value profile counters at compile time. LLVM Profile Warning: Unable to track new values: Running out of static counters. Consider using option -mllvm -vp-counters-per-site=<n> to allocate more value profile counters at compile time. ++ return 1 error: last command exited with $?=1 not ok 5 - pretend we have a fully passing test suite

Ok now I know I have to solve the LLVM generating this issue.

Thanks a lot

Fabio

Show 24 quoted lines

> Il giorno 1 lug 2020, alle ore 18:10, Jeff King <peff@peff.net> ha scritto:
> 
> On Wed, Jul 01, 2020 at 06:00:49PM +0200, Fabio Frumento wrote:
> 
>> I get several messages like this
>> 
>> LLVM Profile Warning: Unable to track new values: Running out of static counters.  Consider using option -mllvm -vp-counters-per-site=<n> to allocate more value profile counters at compile time.
> 
> That could be related. I don't know enough about llvm's profiling to
> say. If it's just a warning and not terminating the process, that might
> be OK. But some of the tests check the stderr from Git. If the profiled
> binaries are producing extra messages, that could cause a problem (and
> it looks like t0410.15 that you posted does make sure stderr is empty,
> so this seems a likely culprit).
> 
>> I’ve checked the scripts in the t folder, they use #!/bin/sh while
>> I’m using zsh could  it be of some relevance? Which shell are they
>> supposed to be run?
> 
> They're generally run with whatever $SHELL_PATH is set by the Makefile
> knobs, which defaults to /bin/sh. The interactive shell you're using
> shouldn't be relevant.
> 
> -Peff