Skip to content
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

Switch to the new ARM64 Helix queues #77764

Merged
merged 3 commits into from
Dec 21, 2022

Conversation

MichalStrehovsky
Copy link
Member

Want to check if this works, no merge for now.

Cc @dotnet/runtime-infrastructure

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@ghost ghost assigned MichalStrehovsky Nov 2, 2022
@MichalStrehovsky
Copy link
Member Author

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ghost
Copy link

ghost commented Nov 2, 2022

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

Issue Details

Want to check if this works, no merge for now.

Cc @dotnet/runtime-infrastructure

Author: MichalStrehovsky
Assignees: MichalStrehovsky
Labels:

area-Infrastructure

Milestone: -

@MattGal
Copy link
Member

MattGal commented Nov 2, 2022

Consider trying ubuntu.2004.armarch / ubuntu.2004.armarch.open as well.

@MichalStrehovsky
Copy link
Member Author

@dotnet/area-system-globalization this is switching the tests from running on Windows 10 ARM64 to Windows 11 ARM64. Is it expected that these tests would fail? Do they need special OS configuration? They're failing both in the regular libraries run and NativeAOT libraries run on ARM64.

[FAIL] System.Globalization.Tests.NumberFormatInfoCurrencyGroupSizes.CurrencyGroupSizes_Get_ReturnsExpected(format: NumberFormatInfo { }, expected: [3, 2])
Assert.Equal() Failure
              ? (pos 1)
Expected: [3, 2]
Actual:   [3]
   at System.Globalization.Nls.Tests!<BaseAddress>+0x89e4b4
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x14c
[FAIL] System.Globalization.Tests.CultureInfoConstructor.Ctor_String(name: "prs", expectedNames: ["prs"], expectToThrowOnBrowser: True)
Assert.Contains() Failure
Not found: fa
In value:  String[] ["prs"]
   at System.Globalization.Tests.CultureInfoConstructor.Ctor_String(String name, String[] expectedNames, Boolean expectToThrowOnBrowser) + 0xa0
   at System.Globalization.Nls.Tests!<BaseAddress>+0x8a7760
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x14c
[FAIL] System.Globalization.Tests.CultureInfoConstructor.Ctor_String(name: "prs-AF", expectedNames: ["prs-AF"], expectToThrowOnBrowser: True)
Assert.Contains() Failure
Not found: fa-AF
In value:  String[] ["prs-AF"]
   at System.Globalization.Tests.CultureInfoConstructor.Ctor_String(String name, String[] expectedNames, Boolean expectToThrowOnBrowser) + 0xa0
   at System.Globalization.Nls.Tests!<BaseAddress>+0x8a7760
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x14c
[FAIL] System.Globalization.Tests.NumberFormatInfoMiscTests.DigitSubstitutionListTest(cultureName: "prs", shape: NativeNational)
Assert.Equal() Failure
Expected: Context
Actual:   NativeNational
   at System.Globalization.Tests.NumberFormatInfoMiscTests.DigitSubstitutionListTest(String cultureName, DigitShapes shape) + 0x54
   at System.Globalization.Nls.Tests!<BaseAddress>+0x89e604
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x14c

@MattGal
Copy link
Member

MattGal commented Nov 2, 2022

@dotnet/area-system-globalization this is switching the tests from running on Windows 10 ARM64 to Windows 11 ARM64. Is it expected that these tests would fail? Do they need special OS configuration? They're failing both in the regular libraries run and NativeAOT libraries run on ARM64.

[FAIL] System.Globalization.Tests.NumberFormatInfoCurrencyGroupSizes.CurrencyGroupSizes_Get_ReturnsExpected(format: NumberFormatInfo { }, expected: [3, 2])
Assert.Equal() Failure
              ? (pos 1)
Expected: [3, 2]
Actual:   [3]
   at System.Globalization.Nls.Tests!<BaseAddress>+0x89e4b4
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x14c
[FAIL] System.Globalization.Tests.CultureInfoConstructor.Ctor_String(name: "prs", expectedNames: ["prs"], expectToThrowOnBrowser: True)
Assert.Contains() Failure
Not found: fa
In value:  String[] ["prs"]
   at System.Globalization.Tests.CultureInfoConstructor.Ctor_String(String name, String[] expectedNames, Boolean expectToThrowOnBrowser) + 0xa0
   at System.Globalization.Nls.Tests!<BaseAddress>+0x8a7760
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x14c
[FAIL] System.Globalization.Tests.CultureInfoConstructor.Ctor_String(name: "prs-AF", expectedNames: ["prs-AF"], expectToThrowOnBrowser: True)
Assert.Contains() Failure
Not found: fa-AF
In value:  String[] ["prs-AF"]
   at System.Globalization.Tests.CultureInfoConstructor.Ctor_String(String name, String[] expectedNames, Boolean expectToThrowOnBrowser) + 0xa0
   at System.Globalization.Nls.Tests!<BaseAddress>+0x8a7760
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x14c
[FAIL] System.Globalization.Tests.NumberFormatInfoMiscTests.DigitSubstitutionListTest(cultureName: "prs", shape: NativeNational)
Assert.Equal() Failure
Expected: Context
Actual:   NativeNational
   at System.Globalization.Tests.NumberFormatInfoMiscTests.DigitSubstitutionListTest(String cultureName, DigitShapes shape) + 0x54
   at System.Globalization.Nls.Tests!<BaseAddress>+0x89e604
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x14c

I saw this. Typically it's because it's the newest windows we've tested on and @tarekgh magically shows up and makes the tests understand the new world and/or fixes the bugs.

@tarekgh
Copy link
Member

tarekgh commented Nov 2, 2022

@MattGal is correct, Windows can change the underlying globalization data. But I expect this test will fail on all Windows 11 and not only arm64 except if the Windows 11 arm64 somehow carries different data. But, in general this shouldn't block the PR as it is most likely a globalization data or test issue.

@MattGal
Copy link
Member

MattGal commented Nov 2, 2022

@tarekgh one thing to note here is that currently the only Windows 11 ARM SKU in Azure is a "preview" SKU; it's slightly newer than the AMD64 versions.

@MichalStrehovsky
Copy link
Member Author

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@MichalStrehovsky
Copy link
Member Author

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@MattGal
Copy link
Member

MattGal commented Dec 20, 2022

Looks like the issues with System.Globalization.Extensions.Nls.Tests continue. Just wanted to add here that it might be time to disable this test on Windows 11 til it can be investigated and fixed to match the changing OS conditions, since we'll be rolling out changes to forward the deprecated Windows 10 ARM queues to the Windows 11 versions next month (approximately 1/11/2023)

@MichalStrehovsky
Copy link
Member Author

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@MichalStrehovsky
Copy link
Member Author

Looks like the issues with System.Globalization.Extensions.Nls.Tests continue. Just wanted to add here that it might be time to disable this test on Windows 11 til it can be investigated and fixed to match the changing OS conditions, since we'll be rolling out changes to forward the deprecated Windows 10 ARM queues to the Windows 11 versions next month (approximately 1/11/2023)

Yeah, I was hoping we wouldn't have to do that, but maybe blocking them just on ARM64 Windows is still fine. We still get results from x64 Windows and chances for an arch-specific bug cropping in globalization while it's disabled are pretty low.

Pushed out a commit that blocks them.

@MichalStrehovsky
Copy link
Member Author

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@build-analysis build-analysis bot mentioned this pull request Dec 21, 2022
@MichalStrehovsky
Copy link
Member Author

Looks good to merge. The failures in the runtime legs are all known per build analysis. Runtime-extra-platforms has a lot of failures but it's par for the course. None of the legs are Arm64 Windows.

@MichalStrehovsky MichalStrehovsky merged commit 8d66372 into dotnet:main Dec 21, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jan 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants