nunit tests fails when run through cc.net saying process timeout. Process has been killed All works fine when through nUNit or VS.
Also cc.net will then show the results of previous build even if the build is a clean one.
Any help plz.
views:
460answers:
4
A:
The default timeout is 600 seconds. If your tests start to exceed that the build will fail with no indication. You may need to up the timeouts for your cc.net nunit task
Arnshea
2009-04-09 14:38:13
<!--Use NUnit for unit testing--> <nunit path="C:\Program Files\NUnit 2.4.8\bin\nunit-console.exe" timeout="6000">This is the copy of my nunit task block in config file, Still they are failing with no reason
sam
2009-04-09 14:43:21
I've seen nunit fail to run on tests that need to run in a Single Threaded Apartment (STA). If that's the case the -nothreaded parameter needs to be passed to nunit-console.exe...
Arnshea
2009-04-09 15:22:34
Yes I am already setting the state to STA in my app.config file of VS project <NUnit> <TestRunner> <!-- Valid values are STA,MTA. WatiN requires STA. --> <add key="ApartmentState" value="STA" /> </TestRunner> </NUnit>Do you want me to set it in ccnet config file
sam
2009-04-09 15:32:15
The only way I was able to get this to work was to change the nunit task to call nunit-console-no-thread.bat - a bat file that you create which calls nunit-console.exe -nothreads %*
Arnshea
2009-04-09 17:36:42
+1
A:
If you are seeing the results from a previous build, it is probably because you are not deleting the results from your previous build.
For example, my NUnit test results are written to files with the name {foo}-results.xml:
<publishers>
<merge>
<files>
<file>bin\debug\*-results.xml</file>
</files>
</merge>
</publishers>
In my tasks, I have a step in my build file that deletes the entire "bin\debug" directory so that my results are always the current ones.
bentsai
2009-05-13 13:34:00
A:
One possibility is that you have a permission issue. CruiseControl is perhaps running under a service account and has different permissions than your user account (which I'm assuming you use to manually run the tests.) Try logging into the machine as the service account, then see if you can run the unit tests through VS or NUnit.
Pedro
2009-05-27 15:16:34
A:
I've seen this happen if a test has an assertion, e.g. Debug.Assert(something here). When this happens to me in CC.Net, the CC.Net build pops up a message box for the assertion. Since no one closes out the message box on the build server, the NUnit test times out.
Adam Tegen
2009-10-29 22:11:52