Intermittent failures after NUnit

Our nightly build is failing.  I've constructed a bootstrap type script that sources/runs the build scripts for 3 projects.  In the last one (but not the first) to run  NUnit, it seems to fail after running it (NUnit).  There are no errors reported by NUnit, but that script fails and therefore fails the entire run.

This is the last output from NUnit:

OS Version: Microsoft Windows NT 5.1.2600 Service Pack 2 .NET Version: 2.0.50727.42

................................................

Tests run: 49, Failures: 0, Not run: 0, Time: 8.781 seconds

After this, the rest of the script fails.  It appears that even though NUnit says the run was okay, either NUnit or FinalBuilder think there was a problem.  I re-run the full build process by hand and everything is okay.  That night, the build works okay.  The next night it fails again.

I found that theres a FinalBuilder 5.192 - I can try that and let you know if I still get the problem.  Should I try that?

 

Hi Brian,

The NUnit action goes on the exit code from NUnit-Console.exe being zero (success), or non-zero (failure), the only exception being if “Fail if no tests pass” is on and no tests are run (in which case FinalBuilder outputs a specific error message “(No tests run)”.)

What version of NUnit are you using? I had a quick look at a copy of the source code I have here, and the source seems fairly clear on returning 0 if there are no failures.

There isn’t any script in any of the action’s script events in FinalBulder, is there? If there is, you’ll see an icon in the rightmost columns of the action entry in the Design page.

The new FB 5 test build you mentioned (192) doesn’t have any changes which relate to the NUnit action in particular, but feel free to try it anyhow if you like.

Regards,

Angus

Angus - thanks for the help.

We’re running NUnit 2.2.9 for .Net 2.0

No, there aren’t any scripts - we haven’t had a need for any yet.

The only other thing I can think of that might possibly be of interest is that the NUnit action is the second action under an action group. The third and last action in the action group is an FxCop action that has been disabled. Finally, the next and last action group starts with a Visual Studio build.

Hi Brian,

I can’t think of anything else off the top of my head, sorry. Would you be able to zip up the FB project and log files (hopefully including a build history which shows the problem occuring) and email the lot to support@finalbuilder.com, please? We can take a look at it here.

Regards,


Angus

After I did some clean up of NUnit test directories and logged the follow on build to a variable, we haven’t had a failure. I don’t know what to say… it’s okay now. Thank you for tyring to help. :slight_smile: – Brian

Hi Brian,

Thanks for keeping us up to date. Hopefully the problem won’t reoccur!

Regards,

Angus