-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Net.NameResolution.Functional.Tests Fails on Android #50928
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/ncl Issue DetailsSystem.Net.NameResolution.Functional.Tests
|
@mdh1418 These tests all appear to pass and can be re-enabled. |
…ng improperly set (#56635) Fixes #50576 Fixes #50881 Fixes #50916 Fixes #50917 Fixes #50918 Fixes #50919 Fixes #50927 Fixes #50928 Fixes #50944 Fixes #50945 Fixes #50946 Fixes #50947 Fixes #50948 Fixes #50999 When setting up functional tests for mobile, the feature switches being used for the tests were misplaced in a broader project, affecting the library tests and causing failures. After moving the feature switches to the scope of functional tests as done in #53253, these test suites no longer fail and can be re-enabled.
System.Net.NameResolution.Functional.Tests
System.Net.NameResolution.Tests.TelemetryTest.EventSource_ExistsWithCorrectId
System.Net.NameResolution.Tests.LoggingTest.GetHostEntryAsync_InvalidHost_LogsError
System.Net.NameResolution.Tests.LoggingTest.GetHostEntry_InvalidHost_LogsError
System.Net.NameResolution.Tests.LoggingTest.GetHostEntry_ValidName_NoErrors
System.Net.NameResolution.Tests.LoggingTest.EventSource_ExistsWithCorrectId
The text was updated successfully, but these errors were encountered: