Long running test hang: System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext

[ViktorHofer]

System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext hangs randomly on OSX.1013.Amd64.Open-x64:Release:

  Discovering: System.Net.Mail.Functional.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Net.Mail.Functional.Tests (found 135 of 136 test cases)
  Starting:    System.Net.Mail.Functional.Tests (parallel test collections = on, max threads = 4)
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:02:00
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:04:01
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:06:02
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:08:03
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:10:04
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:12:06
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:14:07

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.SendMailAsync happens before the TcpListener.AcceptTcpClient (SmtpServer) blocking call?

[ViktorHofer]

@Anipik @danmosemsft I think the bot should not remove labels and milestones that are manually set.

[Anipik]

Yes it’s not meant to do it. I will take a look on why it is removing the label here

[ViktorHofer]

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.

[Anipik]

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

[davidsh]

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.

[ahsonkhan]

Re-opening:
https://helix.dot.net/api/2019-06-17/jobs/ee25291d-b8da-41a2-a8d2-6998a971b0fa/workitems/System.Net.Mail.Functional.Tests/console

Failed on an unrelated PR: #346

netcoreapp-Windows_NT-Release-x86-Windows.7.Amd64.Open
https://dev.azure.com/dnceng/public/_build/results?buildId=445065&view=ms.vss-test-web.build-test-results-tab&runId=14186300&paneView=debug&resultId=180099

Executed on a0019AD

C:\dotnetbuild\work\ee25291d-b8da-41a2-a8d2-6998a971b0fa\Work\1605800a-1e2e-4ac1-949d-deeb631df410\Exec>call RunTests.cmd --runtime-path C:\dotnetbuild\work\ee25291d-b8da-41a2-a8d2-6998a971b0fa\Payload 
----- start Tue 12/03/2019 16:05:17.81 ===============  To repro directly: ===================================================== 
pushd C:\dotnetbuild\work\ee25291d-b8da-41a2-a8d2-6998a971b0fa\Work\1605800a-1e2e-4ac1-949d-deeb631df410\Exec\
"C:\dotnetbuild\work\ee25291d-b8da-41a2-a8d2-6998a971b0fa\Payload\dotnet.exe" exec --runtimeconfig System.Net.Mail.Functional.Tests.runtimeconfig.json --depsfile System.Net.Mail.Functional.Tests.deps.json xunit.console.dll System.Net.Mail.Functional.Tests.dll -xml testResults.xml -nologo -notrait category=OuterLoop -notrait category=failing -notrait category=nonnetcoreapptests -notrait category=nonwindowstests 
popd
===========================================================================================================

C:\dotnetbuild\work\ee25291d-b8da-41a2-a8d2-6998a971b0fa\Work\1605800a-1e2e-4ac1-949d-deeb631df410\Exec>"C:\dotnetbuild\work\ee25291d-b8da-41a2-a8d2-6998a971b0fa\Payload\dotnet.exe" exec --runtimeconfig System.Net.Mail.Functional.Tests.runtimeconfig.json --depsfile System.Net.Mail.Functional.Tests.deps.json xunit.console.dll System.Net.Mail.Functional.Tests.dll -xml testResults.xml -nologo -notrait category=OuterLoop -notrait category=failing -notrait category=nonnetcoreapptests -notrait category=nonwindowstests  
  Discovering: System.Net.Mail.Functional.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Net.Mail.Functional.Tests (found 145 of 146 test cases)
  Starting:    System.Net.Mail.Functional.Tests (parallel test collections = on, max threads = 2)
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:02:06
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:04:18
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:06:30
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:08:42
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:10:42
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:12:42
   System.Net.Mail.Functional.Tests: [Long Running Test] 'System.Net.Mail.Tests.SmtpClientTest.TestCredentialsCopyInAsyncContext', Elapsed: 00:14:42

[danmoseley]

@ViktorHofer if this test happened to hang inside a RemoteExec then we would have stacks, dumps etc. (Due to dotnet/arcade#2919 etc.)

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?

[danmoseley]

cc @stephentoub

[ViktorHofer]

Yes, the VSTest runner allows that.