The more detailed logging is helping, I think.
Hmm… very strange. IWe may need to add more logging and send you another build to get to the bottom of this.
Hi Jamie
Do you logs go back any further? Can you email the logs to us? It looks to us like the server is not seeing the agent registering during the build, so it assumes the agent has gone offline and is stopping the build. The agent log should have more lines like this :
[Registration] Agent has been successfully registered with the Continua server, agent Id is ‘b195eeb2-7056-42a4-a3c1-a16200bdcb35’.
every 30 seconds or so.
Also, are there any errors in the eventlog from the agent?
Yes I get the 30 second “Heart beat” entry in the logs. I’ve emailed both agent and server logs to the support email as they are larger now. To me it just seems like there is a threading/async/task bug that’s bubbling out of the agent/server services.
One of my concerns is the registration on the Continua Server with “LocalHost”. I have multiple sites running on the IIS Server and I use localhost binding for testing server side issues. At the moment I have Localhost binding associated with the “Default Web Site” which is STOPPED. I just wonder if this is part of the communication issue between agent and server services.
Medium: 7:19:00 PM [Agent] Registering agent with hostname ‘JDSRV03’, port ‘9002’ and version ‘1.0.0.2352’ at address ‘localhost’.
Medium: 7:19:00 PM [Debug] Updating registered agent ‘JDSRV03’. Address = ‘localhost’, Port = ‘9002’, Version = ‘1.0.0.2352’
We may have found a possible cause, although we have not been able to reproduce the problem here. I’ll post a new build here for you to try shortly, just bootstrapping a build at the moment with the changes we made this morning which I hope should resolve this issue.
Hi Jamie
Please try this build :
http://downloads.finalbuilder.com/downloads/continua/1.0/ContinuaCI.Server.Setup_x64_1.0.0.2358.exe
http://downloads.finalbuilder.com/downloads/continua/1.0/ContinuaCI.Server.Setup_1.0.0.2358.exe
http://downloads.finalbuilder.com/downloads/continua/1.0/ContinuaCI.Agent.Setup_x64_1.0.0.2358.exe
http://downloads.finalbuilder.com/downloads/continua/1.0/ContinuaCI.Agent.Setup_1.0.0.2358.exe
I’ve been testing for about an 2 hours and I don’t know what you have changed, but stability and consistency have improved immensely. The troubling Continua project/configuration is now behaving very well. Found a missing agent reference as this build 2358 seems to prefer using server agents over build agents, which was part of a hidden issue with the random behaviour of the project build.
So part of the problem I was experiencing was some missing .net Office PIA’s that were not installed on the server/agent and between builds, prior to Continua Build 2358, continua was flip flopping which agent should run a stage. This only became apparent when explicitly reviewing all steps in the log to confirm the process. Again the devil was in the details.
That being said, I still have an issue with 2 unit tests in a stage not executing the second unit test, even if the first action includes failures, but not enough to stop the stage. Just organising some logs for you.
Here is an example of the dual Nunit Actions that are failing to allow the stage to execute both unit tests or "pass" the stage gate. Hope the image helps explain the situation. As you can see I'm trying to get the unit tests for both x86 and x64 in the same stage. In hindsight I wonder if I should be creating multiple stages or configurations to cover these cross platform build scenario's. I'll email the matching Agent/Server logs to the support email.
Attachment unavailable
I think the reason it’s not executing the second NUnit action, even though you probably have the “fail action if any tests fail” option unchecked, is that option is operating on Failures only, and not Errors. The Stage Gate conditions don’t come into play because the Stage failed (a failing action fails the stage), they are only evaluated if the stage succeeds.
We’ll take a look at the NUnit action tomorrow and see what we can do.
My initial thoughts centred around the nunit “Fail action if any tests fail” check box, but in both nunit actions that option is not checked.
I’ve added more comments/log information in https://www.finalbuilder.com/Support/Forums/aft/13034.aspx as this seems more relevant to Nunit issues. Hope all is going well.