-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long-running tests ignored #24
Comments
I can verify that for VS 2012 Update 4 as well. However, I had to increase the time to 10 mins, 4 were not enough (CPU cycle limited?). Thanks for the info, I already spent multiple days with this issue with no clue where to look. At least now it's obvious that this is a test runner issue. |
Hi ! |
Hi Terje, Given that it doesn't happen under the NUnit console or gui runners, I'd On Thu, Feb 13, 2014 at 2:38 PM, Terje Sandstrom
|
As part of our TFS build, we added a post-build event to run the long-running tests in the nunit command line tool and dump them into a text file. There doesn't seem to be another alternative except switching to MSTest. Is there any update or clues of what the cause might be since the bug was reported? |
The root issue is that NUnitEventListener is a MarshalByRefObject. This means it has a default lifetime lease of 5 minutes, with an extension of 2 minutes every time it receives a callback. |
Awesome news! |
I have a pull request out for the fix. |
I have merged in the PR now, and I will add this to the 1.2 release. I will also build a bugfix-release tomorrow with this fix included, for testing/verification. |
Hello Terje, Do you have a bugfix release package available for download? Thanks, Eric From: Terje Sandstrom [mailto:notifications@github.com] I have merged in the PR now, and I will add this to the 1.2 release. I will also build a bugfix-release tomorrow with this fix included, for testing/verification. — |
Hi! (Sorry for the delay - vacation issues :-) ) |
We have some integration tests that can take longer than 2 minutes on our TFS build machine. These are not reported by the test runner.
I have confirmed that this also occurs in VS 2012 Update 2.
It looks like any test that takes longer than 180 seconds is not reported!
Try the below test fixture. Tests "Quick" and "Slow" will be executed and reported; test "Slower" does not appear to even execute, and is shown as 'dimmed' in the Test Explorer window.
Note that all 3 tests will run and get correctly reported by NUnit Console.
The text was updated successfully, but these errors were encountered: