Hi, Thanks for the reply. 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. 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? -Fabio > Il giorno 1 lug 2020, alle ore 17:37, Jeff King <peff@xxxxxxxx> ha scritto: > > On Wed, Jul 01, 2020 at 03:17:05PM +0200, Fabio Frumento wrote: > >> now I'm struggling during the ```make profile``` step >> [...] >> I'm a little surprised as presumed, since 2.27.0 is an official >> release, all the tests should pass without any issue. > > They generally do (not just for releases but for every commit that hits > master). However, we've sometimes seen weird test failures from "make > profile" (which in my experience isn't all that well maintained). > > That said, "make profile" passes for me on v2.27.0, on Linux. It's > possible that a test is racy (the profiler often slows things down, > exacerbating races), but I can't seem to get t0410 to fail with our > usual stress-test to find races. > > If you don't care about profile-optimized builds, then I'd suggest > skipping "make profile". > > If you want to look further into the test failure, probably it would > help to re-run the test with more verbose settings. E.g.: > > [wait for this to fail, which would leave the problematic version of > git in the build directory] > $ make profile > $ cd t > $ ./t0410-partial-clone.sh -v -i -x > > then we could see what's failing. > >> How to file a bug to the Git developers? > > I think you just did. > > -Peff
