Hi guys,
have many successful years using Subversion we decided to move to Git. Our repositories were converted to a Git repositories and pushed to an on premise installation of GitHub enterprise. Unfortunately Continua CI does not seem to like our repository.
Even after two hours after I registered the Git repository in Continua CI the status is still at "Not initialised" and the Continua CI server is constantly at 100% CPU load.
Our environment:
Windows Server 2012 R2
Continua CI 1.7.0.102
Git 2.6.1
I got some warning messages as private messages with some casing problems in the internal Mercurial repository. Hier is a sample of the warning:
Mercurial
Unexpected output while renaming a file with name 'vendor\Rebex\Zip\shared\ZlibDecompressor.cs' to 'vendor\Rebex\Zip\Shared\ZlibDecompressor.cs' in Mercurial repository at C:\ContinuaCI\Rc\276b1c83: vendor\Rebex\Zip\shared\ZlibDecompressor.cs: not overwriting - file exists
This event has been reported 4 times.
Additionally this warning message is logged to the event log:
Repository Monitor
The repository, MailStoreGit, encountered an error while checking for new changesets.
EndInvoke can only be called once for each asynchronous operation.
This event has been reported 138 times
Do you have any suggestions?
Regards
Kay Zumbusch
Hi Kay,
Thank you for reporting this.
The first warning message “Unexpected output while renaming a file” is basically saying that we can not change the case of a directory in our repository class. This is handled and can be ignored. We’ll suppress this in the next version.
We haven’t seen the second EndInvoke message before and it’s difficult to see what could be causing this and the high CPU usage. To investigate further, we will need to look at a debug log.
Can you enable debug logging in the server configuration file? Then restart the Continua CI Server service and reset the problematic repository on the administration page. Wait until new EndInvoke error messages appear in the event log, then send the debug log to support@finalbuilder.com.
Can you also let us know what settings you have specified on your repository, the easiest way to do this is to download a diagnostics report from the link at the top of the event log page and send this to us. Also, if you could provide any further information on the repository, such as size on disk, number of commits, number of branches and usage of submodules, which may help us to troubleshoot this issue.
Hi Dave,
as our repository was converted from a Subversion repository all former SVN branches are included. We have 84 branches and the SVN import with all branches is about 1 GB. I will send the diagnostics file and the debug log to your support after the repo reset is finished.
Regards
Kay Zumbusch