AnalyzerConfigDocumentOpenedClosedEvents is flaky
Runfo Tracking Issue: AnalyzerConfigDocumentOpenedClosedEvents is flaky
| Build | Definition | Kind | Run Name | Console | Core Dump | Test Results | Run Client |
|---|---|---|---|---|---|---|---|
| 1977820 | roslyn-CI | Rolling | Test_Windows_Desktop_Debug_64_Windows.10.Amd64.Open | console.log | runclient.py | ||
| 1967322 | roslyn-CI | PR 63599 | Test_Windows_Desktop_Debug_64_Windows.10.Amd64.Open | console.log | runclient.py | ||
| 1962658 | roslyn-CI | PR 63548 | Test_Windows_Desktop_Debug_64_Windows.10.Amd64.Open | console.log | runclient.py |
Build Result Summary
| Day Hit Count | Week Hit Count | Month Hit Count |
|---|---|---|
| 0 | 0 | 2 |
FYI to @mavasani here.
@vatsalyaagrawal Could we assign this flakiness issue?
@mavasani Can we skip this test for now? It fails very often.
@Youssef1313 Yes
https://github.com/dotnet/roslyn/pull/63352
Looks like AdditionalDocumentOpenedClosedEvents is similarly flaky.
@jaredpar Can you point two runfo tracking issues to the same GitHub bug, or will that make things explode?
That woud be bad