Open 333fred opened 4 years ago
I'll take a look.
Assigning to @sharwell based on the investigations in https://github.com/dotnet/roslyn/issues/46255
@mavasani This doesn't appear to be the same issue as #46255. ☹️
This seems to affect this line: https://github.com/dotnet/roslyn/blob/075e9c3e3e57b150cfae938d4b652b9ee9c4171f/src/Compilers/CSharp/Portable/Binder/Binder_Symbols.cs#L2386
It feels like parallel binding of the same identifier (optimistic initialization) is resulting in a case where one of the side effects (error reporting) is observed from both the path that wins the initialization and the one that doesn't.
The following are known flaky tests within this class:
Details for TestDefaultDiagnosticProviderSemantic
This test has failed 15 times in the last 14 days. Failure message:
Some examples of failures: https://dev.azure.com/dnceng/public/_build/results?buildId=724700&view=ms.vss-test-web.build-test-results-tab https://dev.azure.com/dnceng/public/_build/results?buildId=721954&view=ms.vss-test-web.build-test-results-tab https://dev.azure.com/dnceng/public/_build/results?buildId=718388&view=ms.vss-test-web.build-test-results-tab
One possibly notable detail: failures seem to take ~2.2 seconds for the test to run, successes take under .5 seconds for the most part.
Details for TestDefaultDiagnosticProviderRemove
Builds
Configurations
Details for TestDefaultDiagnosticProviderAll
https://github.com/dotnet/roslyn/blob/1386d0fdd719f0a141d46315582f5b2724719299/src/VisualStudio/Core/Test/Diagnostics/DefaultDiagnosticUpdateSourceTests.vb#L143
Example build: https://dev.azure.com/dnceng/public/_build/results?buildId=749582&view=ms.vss-test-web.build-test-results-tab&runId=23240534&resultId=202015&paneView=debug
Xunit log: