Skip to content

Conversation

@simonrozsival
Copy link
Member

The TimeZoneInfoTests.TestGetSystemTimeZones is failing due to a known issue where on Android we return timezones with duplicate display names (#90269), now we're just seeing it on a more recent Android API levels. This is possibly due to an update to the TZ data.

Closes #121963

/cc @tarekgh @davidnguyen-tech

@dotnet-policy-service
Copy link
Contributor

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

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR marks the TestGetSystemTimeZones test as having an active issue on Android by adding an ActiveIssue attribute. The test is failing on Android due to a known issue (#90269) where timezones with duplicate display names are returned, which has now manifested on more recent Android API levels, likely due to updated timezone data.

Key Changes

  • Added [ActiveIssue("https://github.com/dotnet/runtime/issues/90269", TestPlatforms.Android)] attribute to skip the test on Android until the underlying issue is resolved

@simonrozsival simonrozsival merged commit ffa7570 into main Nov 27, 2025
96 of 97 checks passed
@simonrozsival simonrozsival deleted the dev/srozsival/disable-android-timezoneinfo-testgetsystemtimezones branch November 27, 2025 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[android] System.Tests.TimeZoneInfoTests.TestGetSystemTimeZones failure: Assert.DoesNotContain

3 participants