Where does stderr/stdout go when running nunit?

Hi,

I'm trying to debug a problem with a set of nunit tests which run fine from Visual Studio but hang when run from TeamCity. The build configuration is a vs2008 sln file which uses the nunit 2.5.2 wrapper to run the tests. My problem is that when I look at the <BUILDAGENTHOME>/logs/teamcity-build.log, I'm only getting the high-level caught exception, which is this:

[2009-10-20 11:58:54,743] out - 2009-10-20 11:58:54,509 [4004] WARN  JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)

I suspect what I really need is the stderr from the nunit process itself. Could someone point me in the right direction?

Thanks!

7 comments
Comment actions Permalink

Please specify 'teamcity.agent.dotnet.debug' system property for build configuration to enable more verbose logging from TeamCity related part.

0
Comment actions Permalink

Eugene,

Thanks for the tip. I added the debug property as you suggested but I'm not seeing any additional info in the logs. Perhaps I didn't specify it correctly? It's getting picked up in *teamcity.msbuild.tcargs as

/p:teamcity_agent_dotnet_debug="true"

So I guess my next questions are:

1) is "true" a valid value for this property or should I be setting it to something else?
2) If true is valid, is there somewhere else other than $BUILDAGENTHOME\logs\teamcity-build.log that I should be looking to get the additional debug info?
3) Will adding the debug give me the stderr from the nunit process?

Again, what I'm trying to understand is why the exact same tests run in visual studio but hang when run from teamcity. I'm doing this all from the same box the build agent is running on so would expect the same results.

I'm attaching the log and the properties files for your reference. Any insight you might have would be much appreciated. Thanks!



Attachment(s):
McKesson.TPP.DataAccess.sln.teamcity.patch.tcprojx.zip
McKesson.TPP.DataAccess.sln.teamcity.msbuild.tcargs.zip
teamcity-build.log.zip
0
Comment actions Permalink

Dan,

Sorry for the delay. The question is still relevant? If yes please leave a comment or create a separate thread.

Kind regards,
Marina

0
Comment actions Permalink

Marina,

This question just became relevant for us. We are seeing this in the build log at the end of the tests (they all seem to pass):

{code}

[12:17:38]: [Step 2/2] 2011-06-17 12:17:38,282 [4416] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[12:17:38]: [Step 2/2] 2011-06-17 12:17:38,284 [2620] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
{code}
I've enabled the debug mode per Eugene's suggestion with "true" value. I see other debug messages in the log, but none near or after the WARN above. This build is marked successful in TC 6.5.1 if all tests passed despite the warning. Probably not the behavior we would like. I would really like to know what is causing the exception and would appreciate any pointers on how to discover the cause.
Thanks,
Oleg.
0
Comment actions Permalink

Oleg, let's continue this discussion by email as you wrote this both here and to teamcity-feedback@jetbrains.com.
I'll attach summary here at the end.

0
Comment actions Permalink

Eugene,
can you summarize what is the status?
I also found WARN without any additional information after I had added configuration property.
Thanks!

0
Comment actions Permalink

Access do unloaded app domain exceptions may be caused by unit tests. NUnit unloads app domain that runs tests at the end. TeamCity NUnit runner catches those exceptions and reports it as warnings.

0

Please sign in to leave a comment.