Long running nunit test sometimes loses connection to server

Has anyone seen a message like this?

\[10:48:10\]: \[Package.TestRunCompleted\] Object '/4279a934_372f_438e_b597_8177b584b079/bbbke3p5fmobxt9wiz_jckzj_13.rem' has been disconnected or does not exist at the server.
StackTrace:
at JetBrains.BuildServer.CommonLoggers.Util.StandardOutputsCapturer.Dispose()
at JetBrains.TeamCity.NUnitLauncher.NUnitRunnerBase.Run() in c:\Agent\work\5c63e62d7b319a63\src\NUnitLauncher\src\NUnitRunnerBase.cs:line 129

This sometimes happens on a passing but rather long running nunit test (4-6 minutes) on a TeamCity 3.1.1 installation. It doesn't appear to be related to the length of the test as 4:30 fails, while a 5:20 passes.

Thanks!

3 comments
Comment actions Permalink

Does your tests involve AppDomain, Remoting or something related?
Thanks!

0
Comment actions Permalink

It's actually an nunit test that uses TestComplete 5 to do some UI testing. Running stand-alone, nunit gets the results of each test. When running through TeamCity, although the tests run correctly, TeamCity's nunit runner seems to lose track of the running tests and the log shows all the time spent as belonging to that test step. (other test steps report correctly before this one goes long). It's as though nunit returns too late from the build agent such that the TeamCity server's forgotten about it. (Not blaming TeamCity, I think we're both wondering if there's a place to adjust the timeout but I don't know who is timing out!)

I'll look into the nunit add-on we're using to drive TestComplete and see if there is any info there.

Rob

0
Comment actions Permalink

The question perhaps no longer relevant. If it's not please leave a comment or create a separate thread.

Kind regards,
Marina
0

Please sign in to leave a comment.