Tests stop running on TeamCity after updating test station from Windows XP to Windows 7

We just switched our test station from Windows XP to Windows 7 and unexpected problem appeared.

We run tests using NUnit 2.5.9 and at the end of each build step on Windows XP we were getting warnings from TeamCity:

[16:05:27][Step 2/16] 2013-09-20 16:05:28,181 [watchDog] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[16:05:27][Step 2/16] 2013-09-20 16:05:28,181 [1232] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[16:05:27][Step 2/16] 2013-09-20 16:05:28,181 [2684] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[16:05:27][Step 2/16] 2013-09-20 16:05:28,181 [5940] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[16:05:27][Step 2/16] 2013-09-20 16:05:28,181 [2724] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)

and the following error message window popped up:
error.png

but tests were still running and finishing successfully.

Right now with switching to Windows 7, we are getting those warnings as errors:

[10:48:31][Step 2/16] 2013-09-30 10:48:30,862 [watchDog] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[10:48:31][Step 2/16]
[10:48:31][Step 2/16] 2013-09-30 10:48:30,862 [564] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[10:48:31][Step 2/16] Unhandled Exception: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain.
[10:48:31][Step 2/16] 2013-09-30 10:48:30,862 [5088] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[10:48:31][Step 2/16]
[10:48:31][Step 2/16] 2013-09-30 10:48:30,865 [5840] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null)
[10:48:31][Step 2/16] Unhandled Exception: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain.
[10:48:31][Step 2/16] 2013-09-30 10:48:30,866 [4004] WARN JetBrains.Container.Log4netDefaultLoggerInitializer - Unhandled exception in current domain: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain., , (null).



The same Error message window appears and tests are stop running. The short workaround I found so far is just to close this error window and test are continue to run, but even though all tests are passed succesfully,
I have test project maked in Red(Fail) with "NUnit runner failure" message added.               
I am wondering if there is a way to catch this exception somehow in TeamCity test configuration, or any other proper workaround?
Thanks
5 comments
Comment actions Permalink

Hello,

which version of TeamCity do you use? Your problem seems to be related with following issue http://youtrack.jetbrains.com/issue/TW-19607 there is a dotneptPlugin patch which you may try, let me know if it helped...

regards

Zdenek

0
Comment actions Permalink

Hi Zdenek,
Thanks for prompt reply.
We are using TeamCity Enterprise 7.15, I will take some time to explore thread you provided, will try the patch and let you know the result.

0
Comment actions Permalink

Hi Zdenek,
Even after using new patch and checking 'Run process per assembly' checkbox it didn't help and I am getting the same error messages.
Some additional information that might be useful for you guys:
We are using NUnit 2.5.9 and I did reboot the station after updating to a new patch.
Please let me know if you require any additional information.
Thank you and I hope you will keep me updated since it's high priority issue for our team.

0
Comment actions Permalink

Hello,

I would ask you to create and issue to http://youtrack.jetbrains.com (so you can observe the issue) and please attach there log files, thread dumps (http://confluence.jetbrains.com/display/TCD8/Reporting+Issues) and NUnit runner configuration scrreenshot so developers could take a deeper look into the problem...

regrads

Zdenek

0

Please sign in to leave a comment.