Skip to content
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

Microsoft.CodeAnalysis.VisualBasic.UnitTests.Semantics.BinaryOperators.TestLargeStringConcatenation is flaky #57806

Open
jasonmalinowski opened this issue Nov 16, 2021 · 8 comments
Labels
Milestone

Comments

@jasonmalinowski
Copy link
Member

jasonmalinowski commented Nov 16, 2021

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.

@jasonmalinowski jasonmalinowski added Flaky untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 16, 2021
@jinujoseph jinujoseph added Test Test failures in roslyn-CI and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 18, 2021
@jinujoseph jinujoseph modified the milestones: 17.0, 17.1 Nov 18, 2021
@jinujoseph
Copy link
Contributor

jinujoseph commented Nov 18, 2021

cc @allisonchou as tiger

@allisonchou
Copy link
Contributor

@vatsalyaagrawal Would it be possible to have this flaky test prioritized? We've been hitting it a lot lately in runs.

@jasonmalinowski
Copy link
Member Author

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.

@RikkiGibson
Copy link
Contributor

Is it possible to set this issue up so that runfo starts reporting when this happens?

@jasonmalinowski
Copy link
Member Author

@RikkiGibson I tried. I think there's a long Teams conversation internally about the challenges.

@AlekseyTs
Copy link
Contributor

Do we have a crash dump, or at least a call stack?

@allisonchou
Copy link
Contributor

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.

@jinujoseph jinujoseph modified the milestones: 17.1, 17.2 Mar 2, 2022
@arkalyanms arkalyanms modified the milestones: 17.2, 17.5, 17.5 P1 Oct 3, 2022
@arkalyanms arkalyanms modified the milestones: 17.5, Backlog Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants