I have just upgraded to 1.4.3 from a previous version. It is possible that this problem existed in previous versions too, and I assume based on the release notes of 1.4.3 that previous versions just didn't reported the SVN errors. Now, not only it reports the exception, but also it leaves the project as broken. In fact, someone has to go and trigger a force build for the project to get green again.
I can also confirm that this might happen when someone logs off and CC.Net happens to check for modifications. I am saying this, because for the last 4 days I no one logged into the CC.Net host server. Today, I logged in to do some maintainance, and I got the SVN exceptions in some projects (2 out of 15 or so). Furthermore, I am using Remote Desktop to log into the CC.Net host server. I am also using Subversion 1.5.4. I understand that we are at a point where we are trying to figure out if it is SVN or CC.Net's fault. In the meanwhile, is there a way to lower the SVN block error level that CC.Net uses to mark a build broken? I am logging in to that server frequently and I don't want to always have random projects broken. Thanks
