NUnit.Engine.NUnitEngineException : Unable to acquire remote process agent #1401
Comments
|
From the trace, I'm guessing you are testing an assembly built for X86. Is that so? There is an existing issue related to running X86 test assemblies under .NET Core, which I'm currently working on. WRT using --inprocess, I see that advice given quite often. That option tells NUnit to not create a new process but use the same process that is running the console. It's only possible when running a test that targets the .NET Framework rather than .NET Core. |
|
I did not think so, but I am not entirely sure. Here is the project file for the SUT: Here is the project file for the unit tests: Here is the SLN file: Let me know if you would like a Zip file for the commit representing the point in time at which the logs were generated, then you can dig into whatever you think might be relevant at your convenience. |
|
Is this again a problem with spaces in the agent path? The command line could need additional quotes around the nunit-agent.dll path: I recently encountered the same error "Unable to acquire remote process agent" with console runner 3.17.0 and 3.18.2 (installed via nuget.exe) and a net8.0 agent. I found issue #1206 which is supposed to be fixed since 3.16 but nevertheless for me the problem disappeared when I switched from the user home directory "C:\Users\FirstName LastName\..." to an installation location without spaces below "C:\Tools\...". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been using the test runner in JetBrains, but installed the console runner today and cannot get it to work. My tests all run in JetBrains Rider, they just have looooooooong pauses between each test, which I am hoping that the console runner will avoid.
I installed the console runner and added it to my path in accordance with the answer from [one_mile_run] at https://stackoverflow.com/questions/45482507/how-do-i-install-nunit-3-console-on-windows-and-run-tests.
My SUT assemblies are all Net Standard 2.1, and marked with [assembly: NonTestAssembly]. My test fixtures are in a project targeting Core 3.1.
This is what happens in my terminal when I try to run the unit tests:
Here is the InternalTrace.22360.log file:
Here is the test result xml file:
Here is what happens in the console when I add -inprocess: (Don't know what it does, but it was suggested in some similar discussions.)
That produced InternalTrace.21704.log:
along with InternalTrace.21704.CentralTests.PropertyTagger.dll.log, which only had a single line:
InternalTrace: Initializing at level Debugand a smaller results xml file:
The text was updated successfully, but these errors were encountered: