-
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
Timeouts in System.Text.Json.Tests
on arm32
#67878
Comments
Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis Issue Details
|
Happening here as well: #67676 (comment) |
Hit again in #67635. A bunch of different tests being detected as long running - from one of the logs:
|
There over 50 hits in the past day - marking as blocking-clean-ci. Nothing in the week before that though - some recent change? WorkItems
| where FriendlyName == "System.Text.Json.Tests"
| where Queued > ago(1d)
| where Status == "Timeout"
| where QueueName contains "arm"
| 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 |
cc @ViktorHofer as test monitor -- is this always 32 bit ARM? If so can we disable just for that? |
@krwq would it make sense to move some of the tests listed in #67878 (comment) to OuterLoop? |
I'll disable affected tests for Arm32. |
I didn't notice these timeouts as I only looked at test failures yesterday... Thanks Dan for disabling them. |
This was likely regressed by @krwq in #67838. That slowed things down, which would explain why it's only on Arm; it's also debug only, which is what we see; and it began happening fairly consistently at the moment that PR went in. I think it's easier for me to disable those asserts on Arm. BTW I wrote a script to read the console output for all the failures, and these are the tests that fail -- perhaps the slowest tests that run through the asserts?
|
If someone can sign off on #68027, I'm inclined to merge it immediately since this is failing once every hour. |
Signed off, sorry for the slowdown |
#67858
#67852
The text was updated successfully, but these errors were encountered: