Skip to content
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

Test failure System.Net.Sockets.Tests.LoggingTest.EventSource_EventsRaisedAsExpected #50639

Closed
VincentBu opened this issue Apr 2, 2021 · 4 comments · Fixed by #52602
Closed
Labels
area-System.Net.Sockets disabled-test The test is disabled in source code against the issue test-run-core Test failures in .NET Core test runs
Milestone

Comments

@VincentBu
Copy link
Contributor

Run: runtime-libraries-coreclr outerloop 20210401.4

Failed test:

net6.0-windows-Release-x64-CoreCLR_release-(Windows.Server.Core.1909.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:windowsservercore-2004-helix-amd64-20200904200251-272704c
 -System.Net.Sockets.Tests.LoggingTest.EventSource_EventsRaisedAsExpected

Error message:

Half-way through waiting for remote process.
Memory load: 26

Image Name PID Services 
========================= ======== ============================================
svchost.exe 3536 DcomLaunch, LSM, SystemEventsBroker 
svchost.exe 1508 RpcEptMapper, RpcSs 
svchost.exe 2472 gpsvc, iphlpsvc, ProfSvc, Schedule, SENS, 
 UserManager, Winmgmt 
svchost.exe 2708 EventSystem, nsi, RemoteRegistry 
svchost.exe 4784 Dhcp, EventLog, TimeBrokerSvc, 
 WinHttpAutoProxySvc 
svchost.exe 4392 CryptSvc, Dnscache, LanmanWorkstation, WinR 
svchost.exe 3440 CoreMessagingRegistrar 
svchost.exe 3652 DiagTrack 
svchost.exe 3732 SysMain 
Timed out at 4/1/2021 12:45:37 PM after 60000ms waiting for remote process.
Wrote mini dump to: C:\helix\work\workitem\uploads\2156.pfqf1yf5.auh.dmp
\tProcess ID: 2156
\tHandle: 1868
\tName: dotnet
\tMainModule: C:\helix\work\correlation\dotnet.exe
\tStartTime: 4/1/2021 12:44:37 PM
\tTotalProcessorTime: 00:00:00.3906250

Stack trace
   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 224
   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose() in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 57
   at System.Net.Sockets.Tests.LoggingTest.EventSource_EventsRaisedAsExpected() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/LoggingTest.cs:line 38

@ghost
Copy link

ghost commented Apr 2, 2021

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

Run: runtime-libraries-coreclr outerloop 20210401.4

Failed test:

net6.0-windows-Release-x64-CoreCLR_release-(Windows.Server.Core.1909.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:windowsservercore-2004-helix-amd64-20200904200251-272704c
 -System.Net.Sockets.Tests.LoggingTest.EventSource_EventsRaisedAsExpected

Error message:

Half-way through waiting for remote process.
Memory load: 26

Image Name PID Services 
========================= ======== ============================================
svchost.exe 3536 DcomLaunch, LSM, SystemEventsBroker 
svchost.exe 1508 RpcEptMapper, RpcSs 
svchost.exe 2472 gpsvc, iphlpsvc, ProfSvc, Schedule, SENS, 
 UserManager, Winmgmt 
svchost.exe 2708 EventSystem, nsi, RemoteRegistry 
svchost.exe 4784 Dhcp, EventLog, TimeBrokerSvc, 
 WinHttpAutoProxySvc 
svchost.exe 4392 CryptSvc, Dnscache, LanmanWorkstation, WinR 
svchost.exe 3440 CoreMessagingRegistrar 
svchost.exe 3652 DiagTrack 
svchost.exe 3732 SysMain 
Timed out at 4/1/2021 12:45:37 PM after 60000ms waiting for remote process.
Wrote mini dump to: C:\helix\work\workitem\uploads\2156.pfqf1yf5.auh.dmp
\tProcess ID: 2156
\tHandle: 1868
\tName: dotnet
\tMainModule: C:\helix\work\correlation\dotnet.exe
\tStartTime: 4/1/2021 12:44:37 PM
\tTotalProcessorTime: 00:00:00.3906250

Stack trace
   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 224
   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose() in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 57
   at System.Net.Sockets.Tests.LoggingTest.EventSource_EventsRaisedAsExpected() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/LoggingTest.cs:line 38

Author: VincentBu
Assignees: -
Labels:

arch-x64, area-System.Net.Sockets, os-windows

Milestone: -

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Apr 2, 2021
@karelz karelz added this to the 6.0.0 milestone Apr 20, 2021
@karelz karelz removed the untriaged New issue has not been triaged by the area owner label Apr 20, 2021
@karelz karelz added the test-run-core Test failures in .NET Core test runs label May 4, 2021
@VincentBu
Copy link
Contributor Author

Same test failed with Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Remote process failed with an unhandled exception.

Run: runtime-libraries-coreclr outerloop 20210509.3

Failed test:

net6.0-Linux-Release-x64-CoreCLR_release-(Debian.10.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:debian-10-helix-amd64-bfcd90a-20200121150006

- System.Net.Sockets.Tests.LoggingTest.EventSource_EventsRaisedAsExpected

Error message:

Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Remote process failed with an unhandled exception.


Stack trace

Child exception:
  Xunit.Sdk.DoesNotContainException: Assert.DoesNotContain() Failure
Found:    (filter expression)
In value: ConcurrentQueue<EventWrittenEventArgs> [EventWrittenEventArgs { ActivityId = 00000000-0000-0000-0000-000000000000, Channel = None, EventId = 4, EventName = "Info", EventSource = EventSource(Private.InternalDiagnostics.System.Net.Sockets, ae391de7-a2cb-557c-dd34-fe00d0b98c7f), ... }, EventWrittenEventArgs { ActivityId = 00000000-0000-0000-0000-000000000000, Channel = None, EventId = 4, EventName = "Info", EventSource = EventSource(Private.InternalDiagnostics.System.Net.Sockets, ae391de7-a2cb-557c-dd34-fe00d0b98c7f), ... }, EventWrittenEventArgs { ActivityId = 00000000-0000-0000-0000-000000000000, Channel = None, EventId = 4, EventName = "Info", EventSource = EventSource(Private.InternalDiagnostics.System.Net.Sockets, ae391de7-a2cb-557c-dd34-fe00d0b98c7f), ... }, EventWrittenEventArgs { ActivityId = 00000000-0000-0000-0000-000000000000, Channel = None, EventId = 4, EventName = "Info", EventSource = EventSource(Private.InternalDiagnostics.System.Net.Sockets, ae391de7-a2cb-557c-dd34-fe00d0b98c7f), ... }, EventWrittenEventArgs { ActivityId = 00000000-0000-0000-0000-000000000000, Channel = None, EventId = 4, EventName = "Info", EventSource = EventSource(Private.InternalDiagnostics.System.Net.Sockets, ae391de7-a2cb-557c-dd34-fe00d0b98c7f), ... }, ...]
   at System.Net.Sockets.Tests.LoggingTest.<>c.<EventSource_EventsRaisedAsExpected>b__3_0() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/LoggingTest.cs:line 62

Child process:
  System.Net.Sockets.Tests, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 System.Net.Sockets.Tests.LoggingTest+<>c Void <EventSource_EventsRaisedAsExpected>b__3_0()

@karelz
Copy link
Member

karelz commented May 10, 2021

This started massively failing across all OSs (OSX, Windows, Linux) -- some original timeouts and most Assert failures:
Earlier:

We should disable the test ASAP.

@karelz karelz added the disabled-test The test is disabled in source code against the issue label May 11, 2021
@karelz
Copy link
Member

karelz commented May 11, 2021

Test disabled in PR #52563

@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels May 11, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label May 13, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jun 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Sockets disabled-test The test is disabled in source code against the issue test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants