-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Text.Tests.EncodingExtensionsTests.Convert_Encoder_ReadOnlySpan_IBufferWriter failing on Windows Server 2022 #65026
Comments
Tagging subscribers to this area: @dotnet/area-system-text-encoding Issue DetailsRunfo Creating Tracking Issue (data being generated)
|
Failed in today's rolling build 1599183 Diff: ebcd332...56fcb74 |
The passing run was also on Server20H2, while the failing run was on Server2022. @safern could this failure also be related to the ICU differences in the environment? Asking because this only seems to be on x86 and I saw your comment about x86 in #64827. There are a couple others that seem encoding-related and are failing for x86 on Windows Server 2022 too: |
I wouldn't think that'd be the case because ICU is being loaded correctly (the ICU tests are not failing), and if there was a change in the ICU data for globalization, I guess we would see these fail on x64 (I just double checked and we do run x64 on this platform as well). Adding @tarekgh in case he has more insight. |
@elinor-fung @safern the encoding is independent of the ICU. This failure is not related to ICU. @GrabYourPitchforks may guess what could be the problem here. The failing line is runtime/src/libraries/System.Memory/tests/EncodingExtensions/EncodingExtensionsTests.cs Line 191 in 205f70e
Assert.True(
Encoding.UTF8.GetBytes("Hello" + new string('x', 20_000_000) + "\U00010000" + new string('x', 20_000_000) + '\ufffd').AsSpan().SequenceEqual(writer.WrittenSpan)); |
This is failing always and only on windows.amd64.server2022.open since the queue was enabled, and passing everywhere else. |
The Decoder parallel of this test (
runtime/src/libraries/System.Memory/tests/EncodingExtensions/EncodingExtensionsTests.cs Lines 98 to 100 in 205f70e
|
This is hitting consistently on Server 2022. We will need to update the main runtime pipeline to use a Server 2022 queue soon. @GrabYourPitchforks any ideas what might be going on here? |
Also hit this in an unrelated PR #64952
|
Noting these are different machines (anyway, bad memory usually looks like a bit flip). Quite curious it's always Server 2022 |
@dotnet/area-system-text-encoding could someone please advise? There seems to be a problem on Server 2022 using 32bit dotnet that's impacting other tests as well. This may need a VM setting up. |
It has been most likely fixed by #65490. I am going to close the issue, please reopen it if it fails again. |
Runfo Tracking Issue: system.text.tests.encodingextensionstests.convert_encoder_readonlyspan_ibufferwriter
Build Result Summary
The text was updated successfully, but these errors were encountered: