-
Notifications
You must be signed in to change notification settings - Fork 724
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
SocketException when exploring a test assembly #2036
Comments
You should definitely not be getting a socket exception. However, your repro case is equivalent to just throwing an exception! Since the TestCases static member is being called outside of running the test, it's guaranteed that the current context will be null. This is actually a duplicate of issue #1824 |
The interesting thing is that the context isn't null. If you do |
We believe this was fixed by nunit/nunit-console#223 which will be released as part of NUnit.Console 3.7. If you'd like to confirm sooner that the issue is fixed, please try If it turns out that this does not fix your issue, please open a new issue at https://github.com/nunit/nunit-console/issues. |
Thanks @jnm2. I'll do some testing early next week to verify. |
Seems to be all good. Thanks again @jnm2 and team. |
I'm upgrading my projects from NUnit engine 3.4 to 3.6, using framework 3.6 before and after.
When exploring an assembly for tests, I get the following exception:
I do not get this exception when using
--inprocess
, nor when omitting--explore
.Here's a repro case which fails reliably for me:
The text was updated successfully, but these errors were encountered: