-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
JSON flaky tests #67761
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis Issue DetailsWe're seeing some random JSON tests failing. So far I've seen following types of issues:
related:
|
Seen on PR, seems perhaps we somehow ended up without properties on JsonTypeInfo (or one of the flags preventing serialization to happen)
|
I've had this specific Assert.Contains fail 3 times overnight (out of 4 failures total):
|
@krwq this happened in this rolling build as well: https://dnceng.visualstudio.com/public/_build/results?buildId=1712332&view=ms.vss-test-web.build-test-results-tab&runId=46549310&resultId=144498&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab |
Should we fix the ordering of expected and actual in the asserts meantime.. |
Removing blocking-clean-ci label because most of the flakiness is already fixed and (I think) only remaining issue is also marked with this label. |
moving this to 8 since most of the issues are fixed and we likely won't be able to track the remainder in 7.0 timeline |
I think we can close this under the assumption that the final metadata race conditions have been addressed by #71630. If any remaining test failures crop up we can address them individually. |
We're seeing some random JSON tests failing. So far I've seen following types of issues:
related:
System.Text.Json.Serialization.Converters.ObjectWithParameterizedConstructorConverter
1.TryLookupConstructorParameter` #68584The text was updated successfully, but these errors were encountered: