Hi Raúl, I have been trying to determine who reports the "Caught signal", the SVN client or CruiseControl, butfailed so far. It may actually help in pinpointing the culprit. I have a suspicion that actually SVN is guilty here, and CruiseControl just correctly reports the failing of the SVN executable. That said, still this may be triggered by CruiseControl itself somehow. I have no clue jet what the interaction could be between a user session and the service running in the background using a completely different user account.
With regards, Daniël On Apr 22, 10:00 am, Raúl Nuño <[email protected]> wrote: > Hi Daniël, > > Definitely, the cause of the issue seems to be the logging off. > > I hope it will be fixed in future versions. > > Cheers, > > Raúl > > On 21 abr, 19:12, Daniël <[email protected]> wrote: > > > > > Hi, > > > We are having similar problems with our CrouseControl servers. > > We are running one server with CCNet 1.4.3, which uses the Collabnet > > client 1.5.0. > > We are running another server with CCNEt 1.4.3.20 using Collabnet > > client 1.6.1. > > Bot have SVN problems with caught signals. I tried to find something > > in the logfiles, but unfortunately the give no clue what the signal > > was. > > I have had several occasions where loggin off my remote desktop > > connection to the Winsows 2003 server running CCNet seems to trigger > > the SVN issue for the project it is currently checking. With the > > checkexternals on, and quite a few externals in our projects and a lot > > of project, our buildserver is virtually always checking or building. > > > I hope this helps a bit, > > > Daniël > > > On 21 apr, 12:31, Raúl Nuño <[email protected]> wrote: > > > > For more information, the error occurred after a successful build (23 > > > minutes). > > > > 2009-04-20 17:57:42 (Failed) > > > 2009-04-20 17:34:19 (2) > > > > On 21 abr, 11:06, Raúl Nuño <[email protected]> wrote: > > > > > Hi, > > > > > I have been testing the CCNET server and yesterday I had an exception > > > > when CCNET tried to check for modifications. > > > > > <exception><![CDATA > > > > [ThoughtWorks.CruiseControl.Core.CruiseControlException: Source > > > > control operation failed: svn: Caught signal > > > > . Process command: C:\Archivos de programa\CollabNet Subversion > > > > \svn.exe loghttp://X.X.X.X/svn/Project/Dummy/trunk/source-r > > > > "{2009-04-20T15:34:19Z}:{2009-04-20T15:57:42Z}" --verbose --xml -- > > > > username X --password X --non-interactive --no-auth-cache > > > > en > > > > ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute > > > > (ProcessInfo processInfo) > > > > en > > > > ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.GetModifications > > > > (IIntegrationResult from, IIntegrationResult to) > > > > en > > > > ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications > > > > (ISourceControl sourceControl, IIntegrationResult lastBuild, > > > > IIntegrationResult thisBuild) > > > > en > > > > ThoughtWorks.CruiseControl.Core.IntegrationRunner.GetModifications > > > > (IIntegrationResult from, IIntegrationResult to) > > > > en ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate > > > > (IntegrationRequest request)]]></exception> > > > > > Installed in server: > > > > - CruiseControl.Net 1.4.3 > > > > - CollabNet Subversion Client 1.6.0 > > > > - TortoiseSVN 1.6.0 > > > > > I have a lot of problems with the relationship between CCNET and SVN > > > > ("resource out of date; try updating", "Source control operation > > > > failed: svn: Working copy 'out\main\Release' locked > > > > svn: run 'svn cleanup' to remove locks", some merge errors when > > > > comitting... and more sticky random errors). > > > > > Cheers, > > > > > Raúl- Tekst uit oorspronkelijk bericht niet weergeven - > > > > - Tekst uit oorspronkelijk bericht weergeven -- Hide quoted text - > > - Show quoted text -
