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

Connect_ThrowSocketException_Success failures on Linux #79820

Closed
antonfirsov opened this issue Dec 19, 2022 · 1 comment · Fixed by #80715
Closed

Connect_ThrowSocketException_Success failures on Linux #79820

antonfirsov opened this issue Dec 19, 2022 · 1 comment · Fixed by #80715
Labels
area-System.Net.Sockets disabled-test The test is disabled in source code against the issue test-bug Problem in test source code (most likely)
Milestone

Comments

@antonfirsov
Copy link
Member

Test case: System.Net.Sockets.Tests.ConnectTask.Connect_ThrowSocketException_Success

Error message:

Assert.Fail(): Socket Connect should throw SocketException in this case.

Stack trace:

   at System.Net.Sockets.Tests.ConnectTask.Connect_ThrowSocketException_Success() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/Connect.cs:line 230
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodInvoker.cs:line 59

The socket seems to make a succesful connect to an unrelated dual socket in a parallel test. Can be fixed with a trick like #1481 (comment).

@antonfirsov antonfirsov added area-System.Net.Sockets test-bug Problem in test source code (most likely) labels Dec 19, 2022
@antonfirsov antonfirsov added this to the 8.0.0 milestone Dec 19, 2022
@ghost
Copy link

ghost commented Dec 19, 2022

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

Issue Details

Test case: System.Net.Sockets.Tests.ConnectTask.Connect_ThrowSocketException_Success

Error message:

Assert.Fail(): Socket Connect should throw SocketException in this case.

Stack trace:

   at System.Net.Sockets.Tests.ConnectTask.Connect_ThrowSocketException_Success() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/Connect.cs:line 230
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodInvoker.cs:line 59

The socket seems to make a succesful connect to an unrelated dual socket in a parallel test. Can be fixed with a trick like #1481 (comment).

Author: antonfirsov
Assignees: -
Labels:

area-System.Net.Sockets, test-bug

Milestone: 8.0.0

akoeplinger added a commit to akoeplinger/runtime that referenced this issue Dec 22, 2022
@akoeplinger akoeplinger added the disabled-test The test is disabled in source code against the issue label Dec 22, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jan 16, 2023
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Feb 7, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Mar 9, 2023
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-bug Problem in test source code (most likely)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants