I apologize for not responding earlier... I am working on this and have been since you first wrote. Needed to do a re-fetch on one of the enlistments and it's taking bloody forever... I am keeping an eye on it, though and I'll let you know here once it finishes.
Thank you for the update. If it keeps failing, is there anything what could be done from our side?
The main failing is that it is a CVS repository. This is clearly not our best-performing style of repository. That coupled with the size of the repo is a double-challenge. With a long fetch process the chances of failure from a lost packet or a mis-matched request and response are amplified. We do much more than a garden-variety fetch of the whole repository at a single request. We request the log for each commit, parse it then retrieve that commit and then start over with the next.
Is this data available in another, more advanced repository; possibly in git? Failing that, perhaps Bazaar, Mercurial or (shudder) Subversion? Would you need to give up some historical data to move to a different repository?
Let me know...
The enlistments looks like they are stuck (again?) in the same queue they have been for the last month or so. Is there a way we can poke this from the outside to make it retry?
There is a potential move under way to migrate the spec repository into git, but it's still a ways out. We'll be sure and note the change in enlistments when it happens, but for now this CVS repository is the main game in town!
The fetch goes in and out of "Runtime limit exceeded." about daily which is outside of my control. It may appear to be stalled but it has been making good, if slow, progress and started at 297140 commits and is down to 183438 commits left to process. We started this on 03/Apr/12 and we're somewhat less than half way through. As you can see, CVS is not our best-performing repository handler and this is a pretty large enlistment.
Any questions, please ask them here and I'll continue to monitor the progress daily.
Thanks for sharing those details here. If it's catching up I guess that's a good thing. I'll try to be patient.
Sorry that I need to ask it of you... Hope it finishes before the git becomes available.
We finally managed to move the biggest CVS repository (the one which constantly failing) to git. Should we just add it as another enlistment? What should be done with that CVS one?
Please do add the git as a new enlistment. Once that's done, delete the corresponding CVS enlistment in the enlistment page or go to history, find the place where it was added and undo it (the effect is the same...)
Let me know here and I'll monitor the progress.
P.S. It will be interesting to see how long it takes to update all the remaining enlistments which are 5 months behind.
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.