Uh oh!
There was an error while loading. Please reload this page.
Fix TimeZones Test failure - #60140
Conversation
ghost
commented
Oct 7, 2021
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.
|
ghost
commented
Oct 7, 2021
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.
|
tarekgh
commented
Oct 7, 2021
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
tarekgh
commented
Oct 7, 2021
|
tarekgh
commented
Oct 7, 2021
/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 Nimage 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-HKis 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.