-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Possible race in an Assert recently added to Compilation.GetTypeByMetadataName #59395
Comments
dotnet-issue-labeler
bot
added
the
untriaged
Issues and PRs which have not yet been triaged by a lead
label
Feb 8, 2022
CC @333fred |
jaredpar
added
Bug
and removed
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Feb 16, 2022
333fred
added a commit
to 333fred/roslyn
that referenced
this issue
Feb 18, 2022
Attempt at fixing dotnet#59395. Reviewing the codepath I don't see any other obvious points that could cause the assert to fail, so if it continues to reproduce after this change we can look at further logging to determine the root cause.
We haven't seen another instance of this since my fix to account for multi-threading in cache invalidation, so I'm going to call this fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following assert fails from time to time in context of different unit-tests:
Example #1:
Example #2:
It looks like the assert was added in #58366.
The text was updated successfully, but these errors were encountered: