Hi,

We started getting another error as well in our real project. Not sure if it’s the amount of tests that are getting many which is why it fails or what it is but we didn’t get this error earlier today. We’re constantly writing more tests so it’s increasing all the time and the names are quite long.
I tried to remove a file with tests so we went from 190 to 172 and it worked again.

See attached for error.

Hi,

Thanks for that fix. It improved it a lot.

I finally got some more time to work on our testing and got some more issues like the one above. Got this while trying to debug a single test I think:

[2018-09-20 09:07:26 Error] The parameter cannot be null or empty.
 Parameter name: message
 [2018-09-20 09:07:26 Informational] System.ArgumentException: The parameter cannot be null or empty.
 [2018-09-20 09:07:26 Informational] Parameter name: message
 [2018-09-20 09:07:26 Informational] at Microsoft.VisualStudio.TestPlatform.Common.Logging.TestSessionMessageLogger.SendMessage(TestMessageLevel testMessageLevel, String message)
 [2018-09-20 09:07:26 Informational] at VisualGDBTestExtensionShared.VisualGDBTestExecutor.ReportTestResults(String testContainer, kj1 ctx, IBasicStream stream, Dictionary2 selectedTests, List1 tests, IFrameworkHandle frameworkHandle)
 [2018-09-20 09:07:26 Informational] at VisualGDBTestExtensionShared.VisualGDBTestExecutor.RunTestsInSource(String source, Dictionary`
 2 selectedTests, IRunContext runContext, IFrameworkHandle frameworkHandle)
 [2018-09-20 09:07:26 Informational] at VisualGDBTestExtensionShared.VisualGDBTestExecutor.RunTests(IEnumerable`1 tests, IRunContext runContext, IFrameworkHandle frameworkHandle)
 [2018-09-20 09:07:26 Error] An exception occurred while invoking executor 'executor://visualgdb/TestRunner': The parameter cannot be null or empty.
 Parameter name: message

The other error I got above is a bit tricky because it doesn’t seem to happen when I actually debug the code and neither when we just run the tests like a normal application. But I get it sometimes and when I get annoyed enough by it I’ll investigate more 🙂

• This reply was modified 6 years, 2 months ago by Jensa.
• This reply was modified 6 years, 2 months ago by support. Reason: formatting

Hi,

Today the testhost.x86.exe crashed while debugging some test cases. Was able to repeat it with the diagnostics console enabled and got the following logged:

Exception while forwarding test output: WriteFile failed, win32 error code 109
 ------------------ System.ComponentModel.Win32Exception ------------------
 System.ComponentModel.Win32Exception (0x80004005): WriteFile failed, win32 error code 109
 at u7.s(IntPtr a, Byte[] c, Int32 b)
 at ny.a()

The tests still ran however when it crashed and all completed successfully without errors.

Our biggest problem with these issues is that whenever something crashes or something all tests that wasn’t already run gets removed from the Test Explorer window. Sometimes we can then get them back by simply changing a line of code and getting the test project to build and identify tests again but that doesn’t always help either. Perhaps a workaround would be to not remove any test cases from the test explorer when something goes wrong and simply update the pass/fail of the test cases that did run before the crash. That would at least save us a lot of time so we don’t have to try and get the tests back and when they do the history is then lost.

Regards
Jens Nilsson