On Thu, May 12, 2016 at 08:21:10AM +0200, Torsten Bögershausen wrote: > This is the last log that I see: > [...] > ++ git -C too-many-refs fetch -q --tags
Not surprising. > And this may be the processes : > (Not sure, probaly need to reboot & clean ?) If you're killing the hung test with "^C", you shouldn't need to; that tries to clean up any processes and shut down apache. > /bin/sh ./t5551-http-fetch-smart.sh -x > 73459 ttys010 0:21.45 /Users/tb/projects/git/git.pu/git -C too-many-refs > fetch -q --tags > 73460 ttys010 0:00.40 git-remote-http origin > http://127.0.0.1:5551/smart/repo.git > > ps | grep fetch > 73540 ttys006 0:00.00 grep fetch > 73025 ttys010 0:00.14 /bin/sh ./t5551-http-fetch-smart.sh -x > 73459 ttys010 3:40.70 /Users/tb/projects/git/git.pu/git -C too-many-refs > fetch -q --tags I'm surprised not to see fetch-pack in that list. And to see so much CPU going to fetch itself. But perhaps you are simply at a different stage in the test. 3:40 of CPU time is a lot (the whole thing runs in under a minute on my machine). Hmm. Switching to "pu" seems to make things slow on my machine, too, and the time all goes to fetch. So perhaps there is some recent regression there. It should be bisectable. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
