its been a while, but I see something odd happening on our build server which I hope you can help me with.
I run a team build and let msbuild do all the compiling then in the afterdrop target I run FBCmd task to do some translation work on win32 binaries. For some reason the FbCmd task comes to a halt in one of my actions.
Running the project in FB UI and FBCmd works like a charms (so I thought I was done...).
The action it hangs in is one I wrote in ActionStudio, but that particular action succeeds in two earlier loops and when normally running FB. Anyone noticed something similar and can help me out?
I don’t believe we have seen any reports of this before. Usually when FB Actions fail when run from FB Server or Team Build it has something to do with either permissions, or user profiles or licensing (external apps not finding their license info). Your issue doesn’t sound like any of those issues, so it’s probably best if you email your msbuild project, FB project and the action to support so we can try to reproduce it here (on Tuesday as it’s a holiday here on Monday).
If you haven’t seen this before, let me test a few extra things before getting back to you.
The action that hangs is an action written by me in Action Studio. The action pops out a dialog (no user input required). I wonder if that might cause it to hang. Although it is kind of strange the action completes two times and the third time it hangs.
I changed the allow interactive property for FBCMD in the meantime and am running a build to see if that makes a difference.
It is starting to look strange. I have now seen the process hang in several places. My last attempt would not even start FBCmd. The logfile ends suddenly as well
The command line needs a few extra parameters. I run this build PC as a virtual machine and probably will try to move it to a different PC to see if things start working there (I suspect memory issues). Otherwise I can’t explain the diversity.
That looks very unusual. So you’re using FinalBuilder 4? Are you also using the FinalBuilder 4 FBCmd task (via a UsingTask from the assembly file)?
Is there anything in the Event Log to explain what’s happening? Memory issues are a possibility, but something should have gone in the event log or similar.
Does the build machine keep working after this happens? Does it have adequate virtual memory and free disk space?
can’t test this at the moment. I use the FB4 cmd task that comes with FB. I’ll check the event log when I get back to the office. I think the hang in the log file might be caused by TFS buffering the output and only writing stuff to disk when a buffer is full. I’ll change my fb script to log to a txt file as well to see if I can get any further.