-
Notifications
You must be signed in to change notification settings - Fork 527
Flaky Test: Hang in Libuv and Sockets FunctionalTests/netcoreapp2.1 #2503
Comments
PR to enable diagnostic messages, which should tell us which specific test is hanging: #2505 |
- Required to log long-running tests - Will help investigate #2503
I was able to get a local repro and capture dumps, and the root cause appears to be in the CLR (specifically the GC). Blocked waiting for assistance from the CLR. |
We believe the root cause is managed heap corruption. The ASP.NET team will attempt to find the root cause, which could be in either ASP.NET or CLR code. A separate issue is that once the managed heap is corrupted, fatal error reporting can trigger a deadlock in the GC: https://github.com/dotnet/coreclr/issues/17679. ReprosKestrel.Transport.Libuv.FunctionalTests\bin\Release\netcoreapp2.1http://aspnetci/viewLog.html?buildId=450255&buildTypeId=Lite_KestrelStressTest&tab=buildLog Kestrel.Transport.Sockets.FunctionalTests\bin\Release\netcoreapp2.1http://aspnetci/viewLog.html?buildId=451473&buildTypeId=Lite_KestrelStressTest&tab=buildLog |
I have captured two dumps from hung tests (both in |
According to CI logs, the first instance of this hang was 4/3/18 2:40 PM: http://aspnetci/viewLog.html?buildId=439512&tab=buildResultsDiv&buildTypeId=Lite_KestrelStressTest Earlier this day, the NETCoreApp dependency was updated from NETCoreApp 2.1.0-preview2-26330-03 to 2.1.0-preview3-26331-01: aspnet/Universe@f828c9d#diff-30dcc9789f8ea3c7632e4f054e60c072 It's likely the hang is related to the dependency update, either as a bug in the dependency itself, or a bug in ASP.NET that is exposed by the new dependency. |
This issue was moved to dotnet/coreclr#17716 |
Keeping this issue open until the fix is verified in a prodcon build by ASP.NET. |
@mikeharder Is there any way to run the CI run with private builds of coreclr? |
@sywhang: I verified the Kestrel test hang is fixed when using a private build of the GC with the fix (added you to mail thread). Do you need any further verification from ASP.NET? |
Verified the issue repros in build 2.1.300-preview3-008646 and is fixed in build 2.1.300-rc1-008662. |
Kestrel FunctionalTests are hanging frequently on CI:
KestrelHttpServer
http://aspnetci/viewLog.html?buildId=449083&buildTypeId=Lite_KestrelHttpServer&tab=buildLog&_focus=39538
http://aspnetci/viewLog.html?buildId=445522&buildTypeId=Lite_KestrelHttpServer&tab=buildLog
Win2012-Kestrel
http://aspnetci/viewLog.html?buildId=449994&tab=buildLog&buildTypeId=Lite_KestrelStressTest&logTab=tail
The text was updated successfully, but these errors were encountered: