-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix TimeZones Test failure #60140
Fix TimeZones Test failure #60140
Conversation
Tagging subscribers to this area: @tarekgh, @safern Issue DetailsFixes #60119 Recently, Helix started to use The fix here is to make the test tolerate this case. The test still working properly and validating all installed UI languages time zone display names.
|
Tagging subscribers to this area: @dotnet/area-system-runtime Issue DetailsFixes #60119 Recently, Helix started to use The fix here is to make the test tolerate this case. The test still working properly and validating all installed UI languages time zone display names.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1318301449 |
Fixes #60119
Recently, Helix started to use
Windows 7 N
image in the CI run. This image includes a lot of installed UI languages. The time zone display names depends on the installed localized resources on the path%SystemDirectory%\[Language]\tzres.dll.mui
. For example, if Japanese UI language is installed, Windows will install the file%SystemDirectory%\ja-JP\tzres.dll.mui
. We found on the Windows 7 image, Windows not necessary installing this file for specific language.zh-HK
is the one we encountered which caused the test failure.The fix here is to make the test tolerate this case. The test still working properly and validating all installed UI languages time zone display names.