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

[Android] Disable a socket address test #51226

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

MaximLipnin
Copy link
Contributor

@MaximLipnin MaximLipnin commented Apr 14, 2021

SocketAddressTest.ToString_UnsupportedFamily_Throws test fails on Android in case of AddressFamily.Packet and AddressFamily.ControllerAreaNetwork because it expects PNSE for both address family types but there is no any exception thrown.

This change disables the mentioned test on Android due to different behavior. Also, I'm not sure whether the test has right name.

#47911 (comment)

…mily.Packet and AddressFamily.ControllerAreaNetwork
@ghost
Copy link

ghost commented Apr 14, 2021

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

Issue Details

SocketAddressTest.ToString_UnsupportedFamily_Throwstest fails on Android in case ofAddressFamily.PacketandAddressFamily.ControllerAreaNetwork` because it expects PNSE for both address family types but there is no any exception thrown.

This change disables the mentioned test on Android due to different behavior. Also, I'm not sure whether the test has right name.

#47911 (comment)

Author: MaximLipnin
Assignees: -
Labels:

area-System.Net

Milestone: -

@MaximLipnin MaximLipnin merged commit 3ffaab9 into dotnet:main Apr 15, 2021
@MaximLipnin MaximLipnin deleted the disable_test_on_android branch April 15, 2021 12:06
@ghost ghost locked as resolved and limited conversation to collaborators May 15, 2021
@karelz karelz added this to the 6.0.0 milestone May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants