Process timeout without showing any error in test execution using cc.net

问题

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.

回答1:

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

回答2:

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.

回答3:

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.

回答4:

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.

来源：https://stackoverflow.com/questions/734484/process-timeout-without-showing-any-error-in-test-execution-using-cc-net