Build 926 - Start now build timeline(utc!) + hang on init

Continua CI Bugs
1

I've been trying to manually trigger projects with 2 repositories (one vault and one mercurial). The build just seems to hang. When I try and review the log from that build, which I stopped after 10 minutes or so, I get the following error. I've placed the timeline for the 

I also note, that the timeline information seem to be UTC rather than my local time.

Exception: FaultException`1 
Message: The Log with Path 'J:\Customers\Jenasys\JDContinuaCIServer\Ws\Iims\1043\log' does not exist. 
Stack Trace: at Continua.Modules.Builds.Services.BuildLogService.GetStages(Int32 buildId) 
at SyncInvokeGetStages(Object , Object[] , Object[] ) 
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) 
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) 
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) 
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc) 
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet) 

ContinuaCI_926_Timeline_for_BuildInit.jpg

2

With the log stack trace… did you click the Log tab or did you get that error when the build was running/stopping?

We’re working on the other issues at the moment… more questions to come.

3

How have you setup Continua?
Which machine is your Server and Agent on?
Are they on a domain?
What are the time zones of each machine? (including the client)
What are your Operating system versions?
What browser version are you using?

4

Continua + SQL Server 2012
Agent on same server
Server Windows 2008 R2 + service packs
Services running within domain
Test PC - Windows 7 x64 (running on a different domain, but authenticated back to the server domain).
Test browser Chrome 22.0.1229.79 m
All timezones on server/pc’s running +10hours UTC (Brisbane)

5

The server is sitting right next to me, do you want me to kick it for being naughty?

6

Not unless you want it to behave even worse (or it has SSD’s!).

We have spent most of the morining looking at hangi issue (the log issue is fixed), and I suspect it’s hanging while initializing a repository. Did you have a timeout set on the repositories? If they are new repositories that have not been used before, it’s possible for them to take a while to initialize. We added some more logging to the timeline to show what is happening, but I can tell you that 99% of the work done while the build is in the initilizing state is actually waiting for the reprositories to be initialised. Once a repository has been used for a build, subsequent builds should initialise a lot quicker.

The timezone issue is bit of a mystery. We have some javascript on all pages which detects the user’s timezone from the browser that is passed to the server when you log in, and that is used to convert the dates (which are stored relative to UTC) to your timezone. If you log out an in again do the dates shown change?