-
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
Assertion failed in System.Text.Json.JsonSerializer.LookupProperty #67816
Comments
Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis Issue Details
Failed in #67814
|
A new race condition in the System.Text.Json tests? |
Failed again in #67788 |
I think it's same one surfaced elsewhere #67761 |
@krwq I'm guessing by the stacktrace that this is not related to JsonTypeInfo initialization? Is it a new failure? |
I'm pretty sure it is related to initialization. I suspect that with my changes same thing just shows in different place as I'm changing when initialization happens. |
No hits since the new diagnostics were added. Execute: Web | Desktop | Web (Lens) | Desktop (SAW) https://engsrvprod.kusto.windows.net/engineeringdata WorkItems
| where FriendlyName == "System.Text.Json.SourceGeneration.Roslyn3.11.Tests"
| where Queued > ago(2d)
| where ExitCode > 0
| join Jobs on JobId
| project
Queued,
FriendlyName, ExitCode, Status,
ConsoleUri,
PhaseName = tostring(parse_json(Properties)["System.PhaseName"]),
Pipeline = tostring(parse_json(Properties).DefinitionName),
RuntimeFlavor = tostring(parse_json(Properties).runtimeFlavor),
BuildId = tostring(parse_json(Properties).BuildId),
QueueName, Source then examined the console log. |
@danmoseley actually there seem to be few hits (also I changed to 1D since I merged my second change yesterday):
seems that join is causing to show no results. I'm super surprised by which assert failed - quickly looking at the code further suggests some kind of memory corruption but at the same it's even more interesting why that would be exactly the same place in the code Here are few relevant stacks I found [I'll be updating this once I find new ones]: Stack trace 1, at least 2 hits; error code 134
|
Failed in #68473 with:
|
Failed in #67814
Log + dump: https://dev.azure.com/dnceng/public/_build/results?buildId=1709347&view=ms.vss-test-web.build-test-results-tab&runId=46503608&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab&resultId=190696
The text was updated successfully, but these errors were encountered: