Troubleshooting NUnitLauncher2.0.exe

Every now and again we run into Unit tests that fail in mysterious ways and the lack of verbosity in the output generated by NUnitLauncher2.0.exe is a bit frustrating. Can anyone suggest any way in which we can get a little more information to help us in troubleshooting?
Here's an example of what we see:

Target RunNunitTest_generated:
C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher2.0.exe "http://localhost:9090/RPC2" "19289" "../../test/MyProject\UnitTests\bin\Debug\MyProject.Unit.Tests.dll"
C:\Workspace\CI\MyProject-trunk\src\Solutions\MyProject.sln__generatedBuild1203050488100.msbuild(9,88): error MSB6006: "JetBrains.BuildServer.NUnitLauncher2.0.exe" exited with code 1.
Done building target "RunNunitTest_generated" in project "MyProject.sln__generatedBuild1203050488100.msbuild" -- FAILED.

Now... I can see that NUnitLauncher exited with a code of "1" and I can see that there's a MSBuild error code "MSB6006" which suggests that I might have a problem somewhere. So I can go into my Visual Studio installation and try and turn on verbosity for MSBuild to see if that might get me more information... etc... However, if would be nice if some command-line options for increasing verbosity could be passed to either NUnitLauncher itself or at least to my Visual Studio 2005 solution file build runner.

- Rene

4 comments

Have you tried passing /v:diag as parameter for the build runner?

I was using nunit2.0.exe directly on the command line from ncover and had few problems. The problems I had were usually something funky with the custom version of nunit that tc uses. I only saw problems when using DymanicProxy with Rhino.Mocks.

0

Hello,

Thank you for request. Please create the issue in our jira at
http://www.jetbrains.net/jira/browse/TW


--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Every now and again we run into Unit tests that fail in mysterious
ways and the lack of verbosity in the output generated by
NUnitLauncher2.0.exe is a bit frustrating. Can anyone suggest any way
in which we can get a little more information to help us in
troubleshooting?

Here's an example of what we see:

Target RunNunitTest_generated:

C:\BuildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLaun
cher2.0.exe "http://localhost:9090/RPC2" "19289"
"../../test/MyProject\UnitTests\bin\Debug\MyProject.Unit.Tests.dll"

C:\Workspace\CI\MyProject-trunk\src\Solutions\MyProject.sln__generated
Build1203050488100.msbuild(9,88): error MSB6006:
"JetBrains.BuildServer.NUnitLauncher2.0.exe" exited with code 1.
Done building target "RunNunitTest_generated" in project
"MyProject.sln__generatedBuild1203050488100.msbuild" -- FAILED.
Now... I can see that NUnitLauncher exited with a code of "1" and I
can see that there's a MSBuild error code "MSB6006" which suggests
that I might have a problem somewhere. So I can go into my Visual
Studio installation and try and turn on verbosity for MSBuild to see
if that might get me more information... etc... However, if would be
nice if some command-line options for increasing verbosity could be
passed to either NUnitLauncher itself or at least to my Visual Studio
2005 solution file build runner.

- Rene



0

The output from NUnitLauncher mentions an error in an MSBuild script. When I look around the Build working dir in the BuildAgent though I can't find this generated file. Where can I find it?
: [Target "RunNunitTest_generated" in project "Krusty.sln__generatedBuild1204742395118.msbuild"]

0

Hello,
This file is temporary. It is deleted when build has finished.
Please try looking for that file while build is running.

Thanks!

--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

The output from NUnitLauncher mentions an error in an MSBuild script.
When I look around the Build working dir in the BuildAgent though I
can't find this generated file. Where can I find it?

: [Target "RunNunitTest_generated" in project
"Krusty.sln__generatedBuild1204742395118.msbuild"]



0

Please sign in to leave a comment.