-
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
System.Collections.Concurrent.Tests timeout failures in CI #37186
Comments
Tagging subscribers to this area: @eiriktsarpalis |
@wfurt could you please help me find these timeouts in Kusto? I've tried for a while. I assume I should find Result="Fail" (I don't see a "TimedOut") but I don't find any failures on 5/29. If I look at Duration, eg
I only get 4 hits, and those were test failures rather than job failures. I'm guessing I need to lookin a different way to find jobs that timed out. |
gives me ~ 130 entries including the one @tarekgh reported. The problem is that because the run did no finish and report any results, there are no entries in Jobs table.
with one entry vs empty
|
Thank you @wfurt. Just what I needed. It seems the tests do not normally take long. Of the last couple months, 104 out of 22,461 work items timed out. Those that did not mostly took a minute or so. That suggests they go into a hang state due to a bug, they are not merely slow. WorkItems Randomly sampling the console output of the last ~20 timed out runs, suggests certain tests are usually the long running ones.
But, typically when a job does "hang", there is more than one "hanging" test, eg.,
Which suggests possibly they are interfering with each other. |
Hangs are disproportionately likely to be on Windows (but not exclusively on Windows) WorkItems QueueName count_ WorkItems QueueName count_ |
Next action seems either
|
Again in #39640 |
I was inclined to move this out, but there is a possibility this is a product bug, so it woudl be good to at least attempt to loop it locally. |
There were failures on Windows in #41747: This might deserve a separate issue, but unsure. |
net5.0-Linux-Debug-x64-Mono_release-RedHat.7.Amd64.Open https://helix.dot.net/api/2019-06-17/jobs/7c3e1020-fb91-4832-b4db-c0e1df873655/workitems/System.Collections.Concurrent.Tests/console
https://dev.azure.com/dnceng/public/_build/results?buildId=664284&view=logs&j=b4344b0d-0f92-5d69-ccaf-e0b24fbf14a2&t=555ea487-e6f6-5e9e-ac96-b1fa34f2540d&l=92
The text was updated successfully, but these errors were encountered: