-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extensions doesn't seem to work with svn #74
Comments
Hey @lilireli, |
Hey, I tried different ways. First I used the config file provided as exemple, changing the information I needed (as shown under). I was running the command: ####### config file ###### db_driver = 'mysql' Then I tried to remove this file and rerun cvsanaly with the url still: Finally I tried to check out the project and run the following command in the right folder Now, everything works fine without the extension, but when it comes to the CommitLOC extension either it creates an empty table, either it runs continuously, either it does both. I also tried with metrics, and I have the same. Unfortunately, the repo I'm working on is not public and I cannot provide any access to it |
Have you tried to run the same setup (same version of CVSAnalY, same environment, etc.) with some other (if possible, simple) Subversion repository? Just to discard that there is some trouble with the setup. |
Hi, I tried with a public folder, the problem is the same. However I get the Parsing log for /tmp/extjs (svn) By printing the error I get that cvsanaly cannot run the command: When I try to run it myself, it works. However I'm using a proxy to get Thanks for your help |
I think this is not a bug in CVSAnalY. From my point of view it's a problem related to SVN servers. Usuarlly, SVN servers are slow and commands like
Right now, I have CVSAnalY running using your example. It's up since 314 minutes ago (~5 hours) and now is executing the fifth diff of the list.
So, my impression is when you think CVSAnalY is doing nothing, it is really doing things but very slowly because of the problems with the SVN server. If an exception is raised it might be due to a connection error or similar problems. I fixed the code to know exactly what it is happening when an exception is raised by |
I agree with you, the diff commands are really slow when computed by cvsanaly, I did the same and it was around one hour for one diff. However (and there I'm sorry not knowing more about how svn server works) when I run the same command by myself I can retrieve the result quite quickly (less than 1 minute). Is it normal ? Can't I do anything to speed a little bit up cvsanaly ? |
It's odd. I've been checking it again and it took the same time running the command in a terminal than by CVSAnalY. Maybe, when you run the command, the data was cached in memory but I'm not sure what SVN servers do on these cases. |
I'm having the same problem. I also noticed that the "svn diff" is a slow process. The output log of the respective command is as follow:
|
Hello,
I'm using cvsanaly to parse the logs of one subversion repository, and I tried to run differents extensions (CommitLOC and Metric), they both run at infinite, with no error message. I tried with subset of my repo and they run continuously whatever the size of the repo.
The text was updated successfully, but these errors were encountered: