Rescheduled one failed enlistment which finished OK. All the other enlistments are about 1 hour old. Analysis page is now at May 04 2012 and last commit is at 2012-05-03 (about 12 hours ago).
The failed enlistment is shared with another project.
Please be sure you remind me here if the project stalls again.
Great! It worked like a charm and I added a bunch of more projects to the enlistments. I'll check in the next days if the statistics are updated properly. Thanks for the quick response!
I checked again, and some of our active developers are missing and some of our most active projects had errors. I assume this is my fault since I added many new enlistments at once.
Please reschedule failed enlistments. Thanks!
We have run into a stubborn problem with four enlistments. I have escalated your request to management to see what can be done.
Any luck yet? Sadly the missing enlistments include our most prominent projects.
I've passed on a reminder about this one. Hopefully we'll hear something positive soon. It is odd that all the many enlistments come from the same subversion repository but only these few are having trouble; all the rest are updating regularly.
We are able to process revision 2376 fine but revision 2377 has a problem.
Try - svn log -r 2376 [https://svn.52north.org/svn/swe/; echo $?
svn log -r 2377 [https://svn.52north.org/svn/swe/; echo $?
From my past experience, I suspect this is a UTF-8 encoding issue with the commit message. Would it be possible for you to check?
I am seeing more issues in the commit log. Try -
svn log https://svn.52north.org/svn/swe/; echo $?
revision r2413 is another one.
Dear Abhay, to introduce my self, I am Eike and taking care of the 52°North SVN repos.
I fixed both (2377 and 2412).
In addition, do you have any tool or script to get a list of all broken logs for a certain repository? This might stop the ping-pong we might start playing here.
Kind regards and thanks for your support!
You can keep running following command until you get all the revision in the log and there are no "200 OK" errors at the end.
svn log https://svn.52north.org/svn/swe/
I just ran it and r2400 looks like the next suspect.
Thanks for being patient and using Ohloh, Abhay
Thanks for the hint. Just wrote a script to loop over all revision of a repo. After fixing all errors, I'll come back to you to update the 52N listings.
Kind regards, Eike
Hi Adhay, just to inform you, that I checked all our repos and fixed all issues that were found by my script, so please re-run the stats, if possible. Kind regards and thanks for your support and patience!
Thanks for your hard work! It seems to have paid off. Rescheduled 4 Fetches that had failed and they finished OK. The rest of the enlistments are between 3 days and 20 hours old and should update soon. Analysis page is now at Jun 03 2012 and last commit is at 2012-06-05 (about 22 hours ago).
Please keep an eye on it for us and remind us here if the updates should fail.
Thanks to both of you, the number of code lines must have doubled compared to yesterday, so this seems to be working. And our currently most active developers are definitely better represented now. Good work!
Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.