Build 1.0.0.1773 - Agent synchronization failed

Continua CI Bugs
1

Hello,

 

We are now getting following error on one of our projects:


Importance: Error

Date: Monday, April 08, 2013
Time: 1:32:40 PM

Message:

Stage Controller

Error Initialising Workspace
Exception: Exception
Message: Running C:\Program Files\VSoft Technologies\ContinuaCI Agent\hg\hg.exe failed with return code 255 and error output abort: unknown revision '22550824843f361319bedc0faf6e420a45d1866c'!
 (Args were : archive -r 22550824843f361319bedc0faf6e420a45d1866c -I "re:^((Source.*))$" -X re:^((\^(\\|/)\.hgignore))$ --subrepos -R C:\ContinuaAgent\Repos\2cdc6a4a C:\ContinuaAgent\Ws\12482 --config ui.username=Continua)
Stack Trace:    at Continua.Shared.Utils.Mercurial.Run(ProcessArguments args, String workingDir, Func`2 checkResult)
   at Continua.Shared.Utils.Mercurial.Archive(String repository, String destination, String revision, String includes, IEnumerable`1 excludes)
   at Continua.Modules.Builds.Agent.FileSync.AgentRepositoryCache.<>c__DisplayClassd.b__c()
   at Continua.Shared.Utils.ReadWriteLockList`1.WithReadLock(TId id, CancellationTokenSource cancelTokenSource, Action action)
   at Continua.Modules.Builds.Agent.FileSync.AgentRepositoryCache.Export(String dest, String revision, String includes, IEnumerable`1 excludes, Boolean listFiles)
   at Continua.Modules.Builds.Agent.AgentRepositoryHelper.CopySourceToWorkspace(String filePattern, IEnumerable`1 excludes, String relativeDestination, AgentWorkspaceSyncContext wsCtx, Boolean logRepoFiles)
   at Continua.Modules.Builds.Agent.AgentBuildHelper.SyncSourceFromServer(IEnumerable`1 rules, AgentWorkspaceSyncContext workspaceCtx)
   at Continua.Modules.Builds.Agent.AgentBuildHelper.InitialiseWorkspaceOnAgent(AgentCallbackProxy proxy, TransportContextDTO source, Guid callId)
   at Continua.Modules.Builds.Agent.AgentBuildRunner.OnInitialisingWorkspace(Transition`1 inState)


This occurs on every build attempt. Resetting the repository didn't affect this.

2

Hi Olli

One of our guys saw this issue on his dev machine today, of course when we tried to debug it, it worked fine and we were not able to reproduce it. Try restarting the agent. We’ll take another look at this.

3

Hi Olli

We spent some time on this today, and think we may have fixed this issue, unfortunately we were not able to reproduce the problem, so I’m not 100% certain it’s resolved. I just uploaded a new build with the fix we put in today.