Long running test hang: System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext #490
Labels
Milestone
Comments
|
@Anipik @danmosemsft I think the bot should not remove labels and milestones that are manually set. |
|
Yes it’s not meant to do it. I will take a look on why it is removing the label here |
|
Probably because I added the labels shortly after opening the issue. The bot should probably check if the issue has changed before pushing an update it and rerun the analysis. |
|
okay yeah that must be the case. i thought you added the labels and milestone while creating the issue becoz i remember handling that issue |
|
I don't think we have seen this failure/hang recently. And the referenced CI run is not available anymore (mc.dot.net is not available). So, I will close this issue for now. |
|
Failed on an unrelated PR: #346
|
|
@ViktorHofer if this test happened to hang inside a Most tests don't use RemoteExec. Has there been any discussion/is anything tracking getting such information from a test run that hangs in the test execution process itself? |
Dotnet-GitSync-Bot
added
area-System.Net
untriaged
|
cc @stephentoub |
|
Yes, the VSTest runner allows that. |
|
|
|
Another one - net7.0-windows-Debug-x86-CoreCLR_release-Windows.7.Amd64.Open this test is hanging like this about 5 times a month, every time on a debug runtime: WorkItems
| where Started > now(-500d)
| where FriendlyName == "System.Net.Mail.Functional.Tests"
//| where ExitCode == 139
| where Status == "Timeout"
| join kind= inner (
Jobs | where Started > now(-500d) | project QueueName , JobId, Build, Type, Source, Properties
) on JobId
| summarize count() by ExitCode, QueueName, Source, Started,//=format_datetime(bin(Started, 1d), 'MM-dd-yyyy'),
Pipeline = tostring(parse_json(Properties).DefinitionName),
Pipeline_Configuration = tostring(parse_json(Properties).configuration),
OS = QueueName,
Arch = tostring(parse_json(Properties).architecture),
Finished,
Build = tostring(parse_json(Properties).BuildNumber)
| order by Started asc
|
ghost
added
the
in-pr
ghost
removed
the
in-pr
|
It looks like we are hitting timeouts on a release runtime too. Recent failure: https://dev.azure.com/dnceng/public/_build/results?buildId=1612060&view=ms.vss-test-web.build-test-results-tab&runId=44893928&resultId=198053&paneView=debug Modified version of @danmoseley's query to filter on WorkItems
| where Started > now(-500d)
| where FriendlyName == "System.Net.Mail.Functional.Tests"
| where Status == "Timeout"
| join kind= inner (
Jobs | where Started > now(-500d) | project QueueName, JobId, Build, Type, Source, Properties
) on JobId
| project
ExitCode, QueueName, Started,
PhaseName = tostring(parse_json(Properties)["System.PhaseName"]),
Pipeline = tostring(parse_json(Properties).DefinitionName),
OS = QueueName,
Arch = tostring(parse_json(Properties).architecture),
Finished,
Source,
Build = tostring(parse_json(Properties).BuildNumber)
| where PhaseName contains "release_coreclr"
| order by Started desc
|
radical
pushed a commit
to radical/runtime
that referenced
this issue
Jul 7, 2022
|
No recent hits, not actionable at this moment, closing until issue resurfaces. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContexthangs randomly onOSX.1013.Amd64.Open-x64:Release:https://mc.dot.net/#/user/dotnet-bot/pr~2Fdotnet~2Fcorefx~2Frefs~2Fheads~2Fmaster/test~2Ffunctional~2Fcli~2Finnerloop~2F/20190518.8/workItem/System.Net.Mail.Functional.Tests/wilogs
@stephentoub maybe
SmtpClient.SendMailAsynchappens before theTcpListener.AcceptTcpClient(SmtpServer) blocking call?The text was updated successfully, but these errors were encountered: