-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add more diagnostics to LookupProperty (more diagnostics to flaky tests) #68281
Conversation
Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis Issue DetailsContributes to: #67816 Seems there was more asserts in LookupProperty I missed last time because AggressiveInlining which caused the stack trace to skip the correct method name
|
@@ -172,17 +172,22 @@ public partial class JsonTypeInfo | |||
} | |||
|
|||
// No cached item was found. Try the main dictionary which has all of the properties. | |||
Debug.Assert(PropertyCache != null); | |||
#if DEBUG | |||
if (PropertyCache == null) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC this can only happen during initialization races?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so but I'm not sure how yet, hopefully the DebugInfo will shed some light on the "how"
The failure |
…ts) (dotnet#68281) * add more diagnostics to LookupProperty flaky tests * Fix nullability issue on Release build
Contributes to: #67816
Seems there was more asserts in LookupProperty I missed last time because AggressiveInlining which caused the stack trace to skip the correct method name