nunit-console-x86 crashes with socketexception
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NUnit V2 |
Fix Released
|
High
|
Charlie Poole |
Bug Description
We run our unit tests under a Jenkins build server, via nant.
To run the tests we use the nunit-console as our code is compiled as .NET 4.
<exec program=
workingdi
commandli
We are using NUnit 2.5.10.
However, intermittently we see this exception, which stops our builds:
Unhandled Exception:
[exec] System.
[exec]
[exec] Server stack trace:
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec] at System.
[exec]
[exec] Exception rethrown at [0]:
[exec] at System.
[exec] at System.
[exec] at NUnit.Core.
[exec] at NUnit.Util.
[exec] at NUnit.ConsoleRu
[exec] at NUnit.ConsoleRu
Related branches
tags: | added: console |
Changed in nunitv2: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Charlie Poole (charlie.poole) |
milestone: | none → 2.6.0 |
status: | Triaged → Fix Committed |
Changed in nunitv2: | |
status: | Fix Committed → Fix Released |
I am running into the exact same problem for our unit tests under the NUnit runner on a Bamboo build server. The log shows the exact same error as above.
I was also using local Bamboo variables for the directory path to the DLL to test. The occurances of this error went down considerably when I explicitly indicated the path to the DLL, however the variables are still in there (as they are defined at the Project level and I'm using them for other Plans/Jobs), and the log does show them as environmental variable substitutions when calling NUnit (not that I necessarily think this is the cause, just pointing out similarities).