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
AnalyzerConfigDocumentOpenedClosedEvents is flaky #62479
Labels
Area-Analyzers
Flaky
Infraswat
Tenet-Reliability
Customer telemetry indicates that the product is failing in a crash/hang/dataloss manner.
Milestone
Comments
dotnet-issue-labeler
bot
added
Area-Analyzers
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Jul 7, 2022
FYI to @mavasani here. |
vatsalyaagrawal
added
Integration-Test
Test failures in roslyn-integration-CI
Infraswat
and removed
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Jul 15, 2022
vatsalyaagrawal
added
Flaky
and removed
Integration-Test
Test failures in roslyn-integration-CI
labels
Jul 15, 2022
@vatsalyaagrawal Could we assign this flakiness issue? |
@mavasani Can we skip this test for now? It fails very often. |
@Youssef1313 Yes |
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 |
mavasani
added
the
Tenet-Reliability
Customer telemetry indicates that the product is failing in a crash/hang/dataloss manner.
label
Oct 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-Analyzers
Flaky
Infraswat
Tenet-Reliability
Customer telemetry indicates that the product is failing in a crash/hang/dataloss manner.
Runfo Tracking Issue: AnalyzerConfigDocumentOpenedClosedEvents is flaky
Build Result Summary
The text was updated successfully, but these errors were encountered: