Open jasonmalinowski opened 2 years ago
cc @allisonchou as tiger
@vatsalyaagrawal Would it be possible to have this flaky test prioritized? We've been hitting it a lot lately in runs.
So this got flakier once we enabled the test dumping support; we're still not entirely sure why. The one belief was that the dump support slowed down the test just a hair, but that may not be the case.
Is it possible to set this issue up so that runfo starts reporting when this happens?
@RikkiGibson I tried. I think there's a long Teams conversation internally about the challenges.
Do we have a crash dump, or at least a call stack?
This might be a partial stack trace (taken from here):
The active test run was aborted. Reason: Test host process crashed
The active Test Run was aborted because the host process exited unexpectedly. Please inspect the call stack above, if available, to get more information about where the exception originated from.
The test running when the crash occurred:
Microsoft.CodeAnalysis.VisualBasic.UnitTests.Semantics.BinaryOperators.TestLargeStringConcatenation
This test may, or may not be the source of the crash.
Test Run Aborted with error System.Exception: One or more errors occurred.
---> System.Exception: Unable to read beyond the end of the stream.
at System.IO.BinaryReader.Read7BitEncodedInt()
at System.IO.BinaryReader.ReadString()
at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()
at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action`1 errorHandler, CancellationToken cancellationToken)
--- End of inner exception stack trace ---.
I'm not seeing anything else unfortunately.
It's crashing the test process so we don't get usual logs. Runfo doesn't support making a tracking bug, but you can click here to view impacted builds from the last 24 hours.