-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
System.Text.Json.Tests.Utf8JsonWriterTests.WriteNumbers failing in runtime-extra-platforms #65019
Comments
Tagging subscribers to this area: @dotnet/area-system-text-json Issue DetailsRunfo Creating Tracking Issue (data being generated)
|
Failed in build 1599183 Diff: ebcd332...56fcb74 |
This is the only time this test has ever failed. I don't see any plausible changes in the diff range, so I think it's sporadic. We will have to wait and see whether we get a pattern in future events. TestResults
| join kind=inner WorkItems on WorkItemId
| join kind=inner Jobs on JobId
//| where Started >= datetime(2022-01-01)
| where Result == "Fail"
| where Method == "WriteNumbers"
|
Yeah, we seem to have a bunch intermittent failures after the move to Windows.Amd64.Server2022 (switch only finished yesterday, so we don't have a huge number of builds yet). There's a lot of 'red' in that leg - trying to open tracking issues for them all, so we have a better idea of what is affected. Not sure if any/all are related, but a number of intermittent test failures seem to involve string encoding (at least as someone unfamiliar with them looking at the call stacks / names). |
I re-ran @danmoseley's query today and it looks like this was a one-off occurrence. Should we close this? |
Closing for now. I'm guessing this would be re-filed if the test failure occurs again? |
Runfo Tracking Issue: System.Text.Json.Tests.Utf8JsonWriterTests.WriteNumbers failing in runtime-extra-platforms
Build Result Summary
The text was updated successfully, but these errors were encountered: