system.globalization.tests.icutests.icushouldbeloaded

[runfoapp]

Build	Kind	Start Time
1589182	PR 62740	2022-03-02
1589203	Rolling	2022-03-02
1589450	PR 64743	2022-03-02
1589641	PR 64567	2022-03-02
1590183	PR 64330	2022-03-02
1590727	Rolling	2022-03-02
1590775	PR 64759	2022-03-02
1590822	PR 64766	2022-03-02
1591380	PR 64759	2022-04-02
1591573	PR 64766	2022-04-02
1591711	Rolling	2022-04-02
1591751	PR 64330	2022-04-02
1591746	PR 64800	2022-04-02
1592091	PR 64734	2022-04-02
1592314	PR 64743	2022-04-02
1592168	PR 64800	2022-04-02
1596337	Rolling	2022-07-02

[ghost]

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

Issue Details

---

Runfo Creating Tracking Issue (data being generated)

Author:	runfoapp[bot]
Assignees:	-
Labels:	area-System.Globalization, untriaged
Milestone:	-

[safern]

This is a fallout from updating the helix queues to Server20H2. @tarekgh do you happen to know if Server20H2 no longer carries ICU with it?

[tarekgh]

@safern My understanding is it should have the ICU. I'll try to ask around or if we can get access to the helix machine we can check quickly.

[safern]

I'm getting a VM to see what's going on.

[safern]

@tarekgh and I got to the VM and figured out that these new helix machines don't have icu.dll on SysWOW64 and the tests are running on x86, so that's why we can't find icu.dll. I'm following up with @MattGal to see what we can do.

[sbomer]

Still failing in runtime-extra-platforms

[tarekgh]

@safern we may add some checks in the test to protect more against such cases? I am seeing it is good to catch such cases but in same time we need to avoid CI interruptions I guess.

[safern]

@safern we may add some checks in the test to protect more against such cases? I am seeing it is good to catch such cases but in same time we need to avoid CI interruptions I guess.

Yes, now that I've confirmed that this is a server core issue we should add it to the condition to not run them when in server core and x86.