Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
"Timeout of 60000 expired" is misleading
Options
Previous Topic Next Topic
sferencik
#1 Posted : Monday, April 22, 2013 6:30:21 AM(UTC)
Rank: Member

Groups: Registered
Joined: 4/4/2013(UTC)
Posts: 16
Location: Czech Republic

Thanks: 4 times
Was thanked: 1 time(s) in 1 post(s)
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".
Back to top
Remco
#2 Posted : Monday, April 22, 2013 9:53:26 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks for reporting this. I'll take a look and will see if a fix is possible.

Cheers,

Remco
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.022 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download