[mobile] Skip localhost subdomain with trailing dot test on Android#127862
Open
github-actions[bot] wants to merge 2 commits intomainfrom
Open
[mobile] Skip localhost subdomain with trailing dot test on Android#127862github-actions[bot] wants to merge 2 commits intomainfrom
github-actions[bot] wants to merge 2 commits intomainfrom
Conversation
The test DnsGetHostEntry_LocalhostSubdomainWithTrailingDot_ReturnsLoopback expects DNS queries for `*.localhost.` to resolve to loopback, but Android devices resolve these to actual network addresses. Related to existing ActiveIssue for DnsGetHostEntry_LocalhostSubdomain_ReturnsLoopback which has the same root cause. Fixes #126456 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Tagging subscribers to this area: @karelz, @dotnet/ncl |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses a platform-specific test failure in System.Net.NameResolution functional tests by skipping an RFC 6761 localhost-subdomain test case on Android, where the platform DNS resolver does not consistently return loopback addresses for *.localhost. names.
Changes:
- Mark
DnsGetHostEntry_LocalhostSubdomainWithTrailingDot_ReturnsLoopbackas an active issue on Android using existing issue#126456.
Show a summary per file
| File | Description |
|---|---|
| src/libraries/System.Net.NameResolution/tests/FunctionalTests/GetHostEntryTest.cs | Adds an [ActiveIssue] skip on Android for the trailing-dot localhost subdomain loopback assertion test. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 0
This was referenced May 6, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reasoning
The test
DnsGetHostEntry_LocalhostSubdomainWithTrailingDot_ReturnsLoopbackexpects DNS queries for*.localhost.(with trailing dot) to resolve to loopback addresses, following RFC 6761. However, on Android devices, these queries resolve to actual network addresses (both IPv4 and IPv6) instead of loopback.This is the same root cause as
DnsGetHostEntry_LocalhostSubdomain_ReturnsLoopback(without trailing dot), which is already disabled on Android via ActiveIssue #126456. Android's DNS resolver does not treat.localhostsubdomains as reserved names that must resolve to loopback, regardless of whether a trailing dot is present.Adding the same
[ActiveIssue]attribute to this test variant ensures consistent behavior across all localhost subdomain test cases on Android.Impact on platforms
Failing on Android in build 1406427 (2026-05-03):
Errors log
From android-arm64 Helix work item
System.Net.NameResolution.Functional.Tests(console log):First build it occurred
First observed (within the scanned window) in build 1406427, finished on 2026-05-03T09:02:27Z.
Note: This test failure has the same root cause as existing issue #126456, which has been present since April 2026. The "first occurrence" reflects only the scanned window, not the true origin.
Note
This change was generated by the Mobile Platform Failure Scanner workflow.