Build/Test Issues

"Timeout of 60000 expired" is misleading

Started by sferencik on 7,298 views

I have an NUnit test with a TimeoutAttribute. NCrunch correctly respects this time-out limit but still writes "Timeout of 60000 expired" when the time-out happens. The value of 60000 is incorrect as my time-out value is different.

To reproduce, use [Timeout(1)] on an NUnit test. The test should time out and ideally say "Timeout of 1 expired" but instead will report "Timeout of 60000 expired".
Thanks for reporting this. I'll take a look and will see if a fix is possible.

Cheers,

Remco

Post a reply

Log in to reply.