-
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.Security.Cryptography.Tests timing out in the CI #64389
Comments
Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones Issue Detailshttps://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-64365-merge-bf31f3469b0e48fbb4/System.Security.Cryptography.Tests/1/console.3897f734.log?sv=2019-07-07&se=2022-02-16T17%3A44%3A22Z&sr=c&sp=rl&sig=5YFpNB90cUSCQM53WKijNhCJtNGb%2BH1agUVjQQE%2BOTg%3D
|
A workaround is in progress. |
This has happened again for rolling build #20220308.49 on lane |
Should we disable the test for now? It seems that the workaround mentioned on Jan 27th hasn't arrived yet. And I saw this being hit on rolling build quite often. |
@fanyang-mono The specific problem that this issue is looking at is the tests finishing in a reasonable amount of time, then the process hanging after printing results, and thus timing out in Helix (it also was only for Windows 11 (maybe also 10?), IIRC):
The work item you linked to shows two failures, both of which have console logs that show success, but neither of which include the message of the command timing out and being killed by the runner. The test causing the original problem to appear has been deactivated. If there's anything more here, it would be a separate thing to track and resolve. |
Still exisiting: #66694 |
@bartonjs I see. Thanks for the clarification. |
This exact timing out issue is still happening on build |
Hm. That certainly is an "after finishing the process hung"-looking console log. Unfortunately, it's not reproing on my machine, which means it's hard to figure out what tests we're running that Windows has regressed. |
Is it possible for us to get a mini dump when a test run is killed for timing out? |
Using this query
I see a bunch of hangs in ReadAsync_CancelPendingTask_ThrowsCancellationException until 4/7 when fixed by #66694. Zero hangs since. |
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-64365-merge-bf31f3469b0e48fbb4/System.Security.Cryptography.Tests/1/console.3897f734.log?sv=2019-07-07&se=2022-02-16T17%3A44%3A22Z&sr=c&sp=rl&sig=5YFpNB90cUSCQM53WKijNhCJtNGb%2BH1agUVjQQE%2BOTg%3D
https://dev.azure.com/dnceng/public/_build/results?buildId=1575063&view=logs&jobId=bf603221-817a-5f42-894a-9eb35c3c7f97&j=bf603221-817a-5f42-894a-9eb35c3c7f97&t=c8a637da-bfd7-5afe-0aba-62ddf378e6cc
The text was updated successfully, but these errors were encountered: