Pierre, Thanks, I will pass on the suggestion. Hopefully we will get the update system so that a failure like this is a rare occurrence. Have seen some positive movement in that direction already ... [More] and hope for more change soon. We're looking for ways to more intelligently handle failures that aren't under our control. Thanks again! [Less]

mdpdev, Needed to re-fetch one of the enlistments which had failed. All jobs have now run to completion. Please check the results and respond here if any remaining problems show. Thanks!

Victor, Just confirming what you found as well. Getting updates just about daily now. Thanks!

Jack, All jobs finished OK 18 hours ago. Thanks!

skippybosco, The second (non-sourceforge) enlistment for this project can no longer be reached (Host not found). Please notify manager to revise/delete this enlistment. This (sourceforge) ... [More] repository is synchronized with our internal SVN repository (which is not publicly available) several times a day. Thanks! P.S. Please leave a note here once the enlistment is changed and I'll restart the process (although it may restart itself in a couple of days either way.) [Less]

Rescheduled the failed job and it ran to completion OK. Looks like a temporary error while communicating with the repo. svn: Server sent unexpected return value (403 Forbidden) in response to OPTIONS request Should be all set now. Thanks!

Julio, Looks as if all enlistments for this project are working properly today. Ohloh update completed about 8 hours ago. Thanks!

Daniel, Enlistment is back on track. Looks like a transient error at the repo caused the failure. As far as the negative counts are concerned, we are aware that there is a bug in the line-counting ... [More] process. The cause is thought to be long-term tracking of trunk and branch commits and getting confused when branches appear and disappear and sometimes are merged back with the trunk. This is especially difficult considering all the different source control systems we support. We do have an issue in-place for tracking this and a plan for the implementation of the fix. Thanks for your patience! [Less]

Marc, Did a re-fetch on the project and all jobs ran OK. Looked like some kind of error during the git checkout which may have been local or at the repo hung up the previous update. Thanks!

westi, Looks like stats were updated 18 Dec. so the last enlistment must have run OK. The problem is, with this many enlistments, the chances of random failure are multiplied. Please start a new ... [More] post here should the project get stuck again. Thanks! [Less]