MSbuild hanging
Hi,
I installed a new machine with the new version of team city (6.0.2) and moved my MSbuild configuration over. Running the build it works fine to the point Starting: C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.MsBuildBootstrap.exe /workdir:F:\Builds\MessageGateway\Source /msbuildPath:C:\Windows\Microsoft.NET\Framework\v3.5\MSBuild.exe
And then it just sits there I've left it on an earlier build for 8 hours overnight just to see if it was a performance thing. Didn't do anything. I ran the MSBuild script from the command prompt and that worked fine. I've gone to an older machine that used to run (5.1.4) added my build script to it and it ran the whole thing fine not a problem.
After I dug up the log on the agent I noticed that it had gone far in the build I ran over night but took 3 hours which I don't think is right since it ran in seconds on the older version. Any ideas?
I'm trying to run this on a windows 7 X64 machine.
Attachment(s):
teamcity-build.log.zip
teamcity-agent.log.zip
Rianu_MessageGatewayWS_7.log.zip
Server-threadDump.txt.zip
Please sign in to leave a comment.
Hi James
Thank you for detailed description and logs.
Can I ask you to also take an agent thread dump.
Thanks
Michael
Hi Michael
Attached are the files, I think these are right.
Attachment(s):
threadDump-2011-02-28_23.43.39.txt.zip
teamcity-build.log.zip
teamcity-agent.log.zip
Thank you for logs. It was a mistake in requesting you to take agent's thread dump. Could you please attach thread dump of the build. You may find the link 'View thread dump' in the running build overview tab.
Do you use custom tasts? Do you run unit tests?
What processes are running under the build agent process?
Some started commandline tools may stuck waiting commandline input.
Does your build working from commandline on the same folder under the same user account?
What if F:? Is it a network drive or a local drive?
I added that last night,
nope no custom tasks or unit tests. I removed them all. It's just a build.
The MSBuild script executes fine from the cmd line. The F:\ is a local drive
Please try to check running processes under the build agent process to find the process that is hunging. Please capture build thread dump as I asked in the provious post.
Do you use <MSBuild> taksk in your project?
MSBuild runner generates wrapping build script that imports original build script. Could this make it start infinite loop?
It is an MSBuild task, the build script executes fine.
I've tried the same MSBuild script on an older version of Team city and it works fine there.
When I go to get the thread dump from the running build under view thread dump I get "Error -68. Failed to get thread dump from non-java process."
Could you provide a sample build script for me to reproduce the issue?
Do you know when build script hunds?
Build script attached.
Attachment(s):
MessageGatewayWS.proj.zip
Do you have custom pre/post actions in your solution? What actions? What processed do you run?
Could you please try usgin Visual Studio sulution runner to check if the build will hung. You may run your solution without writing a wrapping msbuild script.
no custom pre actions,
It runs fine VS and works fine with the MSBuild on it's own, only when I try to run it with TeamCity that it won't work.
There is a build runner in TeamCity called Visual Studio (sln). What I meant was to try using it to check if the build will succeed.