You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2021. It is now read-only.
I'm using the gitant task "git-info" within several ant projects to retrieve git information for code tagging.
This runs fine within many projects, but with some the invocation of git-info takes terribly long (over 10 minutes to return!) and burns the CPU.
So far, I was not able to figure out any reason for that.
The underlying git repository isn't very large (in comparison to others where git-info is running fine).
Monitoring the JVM (ant) didn't show significant GC activity but high CPU load.
I tried "git gc" and "git fsck" to clean/fix any potential anomalies within the git repository, but no effect.
Any hints welcome.
The text was updated successfully, but these errors were encountered:
Well, first glance on the dump shows that there are an awfull lot of recursive "findFirstReachable" calls. But I don't think that you could actually produce a cycle in your git graph. Maybe you can path it to show what it actually does at that point. I guess you can't give me the repository?
By now, the repository has advanced with new labels and branches, so that I'm currently unable to reproduce the problem.
If there is anything despite that you would like me to test or provide, let me know.
In any case, I'll keep this on my radar and post any new findings as soon as this happens again.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using the gitant task "git-info" within several ant projects to retrieve git information for code tagging.
This runs fine within many projects, but with some the invocation of git-info takes terribly long (over 10 minutes to return!) and burns the CPU.
So far, I was not able to figure out any reason for that.
The underlying git repository isn't very large (in comparison to others where git-info is running fine).
Monitoring the JVM (ant) didn't show significant GC activity but high CPU load.
I tried "git gc" and "git fsck" to clean/fix any potential anomalies within the git repository, but no effect.
Any hints welcome.
The text was updated successfully, but these errors were encountered: