Repository navigation
[release/11.0] [Test Only] Accept both ICU mappings for Pacific Standard Time in Canada - #136980
Merged
Merged
Conversation
<!-- --> ## Summary Allow `IdsConversionsWithRegionTest` to accept either `America/Vancouver` or `America/Los_Angeles` when converting `Pacific Standard Time` with region `CA`. The result depends on the ICU mapping data installed on the test host. The theory now takes a `params string[]` of expected IANA IDs and checks that the returned ID is in that set. All other cases retain a single accepted value. No product behavior changes. ## Validation ```powershell & .dotnet\dotnet.exe build src\libraries\System.Runtime\tests\System.Runtime.Tests\System.Runtime.Tests.csproj /t:Test /p:XunitMethodName=System.Tests.TimeZoneInfoTests.IdsConversionsWithRegionTest ``` Passed: build completed with zero warnings and errors; all 23 theory cases passed with zero failures or skips. ```powershell git --no-pager diff --check ``` Passed. Validation used this Windows host's ICU 72.1 mapping, which returns `America/Vancouver`. Execution with updated ICU data was not tested locally. Resolves #136758 Co-authored-by: Tarek Mahmoud Sayed <tarekms@ntdev.microsoft.com>
|
Azure Pipelines: Successfully started running 3 pipeline(s). 12 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Tagging subscribers to this area: @dotnet/area-system-datetime |
jeffhandley
approved these changes
Nov 4, 2026
Member
|
/ba-g the failures are unrelated and the test changed in this PR is passing. |
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.
Backport of #136942 to release/11.0
/cc @tarekgh
Customer Impact
[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
[How was the fix verified? How was the issue missed previously? What tests were added?]
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]
IMPORTANT: If this backport is for a servicing release, please verify that:
release/X.0-staging, notrelease/X.0.release/X.0(no-stagingsuffix).Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.