-
Notifications
You must be signed in to change notification settings - Fork 150
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
RemotingException when performing multiple runs in a single process #325
Comments
Thanks for the repro @yaakov-h. I can reproduce this. Cutting out the custom runner functionality, an exception can also be seen with the following command line in the nunit-console:
In this case, "NUnitGuineaPig.dll just contained a single class which was:
Running --inprocess instead gives the below exception - I imagine it's likely the two are related however:
|
@yaakov-h I believe this is the issue, however, I'm not sure what the solution should be! |
I'm closing this in favour of nunit/nunit#2614 - now @CharliePoole's confirmed my suspicions. @yaakov-h - please feel free to follow the new issue, and if it doesn't fix your problem once it's in, we can revisit this issue. |
I've come across a strange edge case with the NUnit engine.
As background info - I'm using the NUnit Engine APIs directly in order to integrate it into an in-house distributed CI system.
I have a particular assembly which uses
TestContext.Current.TestDirectory
inside aTestCaseSource
- this was previously discussed at nunit/nunit#2036When calling
ITestRunner.RunTests(listener, filter)
, the engine behaves as expected. When calling it a second time, however, the result XML has zero tests run, zero passed, zero failed.I've posted a repro case to https://github.com/yaakov-h/NUnitMultiRunRepro
If you build it and run:
the engine passes the test the first time, but the test case source failed on subsequent runs with a RemotingException due to some sort of IPC failure:
If I keep the
ITestRunner
alive and re-use it, then I don't see this issue, which would suggest that the engine isn't handling multiple runners correctly.If you add a test to the test filter - for example:
then NUnit doesn't discover anything or print the above error. Instead, it produces the following XML:
The text was updated successfully, but these errors were encountered: