IDN test failure on .NET 8.0

[tarekgh]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=888621
Build error leg or test failing: System.Globalization.Tests.IdnMappingIdnaConformanceTests.GetAscii_Invalid
Pull request: #110492

Error Message

Expected IdnMapping.GetAscii("xn----ufo9661d.xn--r5gy929fhm4f") to throw an ArgumentException. Line Number: 6126

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "to throw an ArgumentException. Line Number: 6126",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

We made fixes last year that need to be backported to release/8.0. These probably should have been backported at the time of the earlier PR. Not a criticism but just an observation. This type of change typically affects all the distros in a staggered fashion and affects our LTS versions.

Related:

• Fix System.Globalization.Extensions.Tests for icu 74/unicode 15.1 #105282
• release/8.0-staging -- Update Alpine and Fedora versions #110492

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=888621
Error message validated: [Expected IdnMapping.GetAscii to throw an ArgumentException. Line Number: 6126]
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 12/7/2024 3:35:12 AM UTC

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=888621
Error message validated: [to throw an ArgumentException. Line Number: 6126]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 12/7/2024 3:36:45 AM UTC

Report

Build	Definition	Test	Pull Request
894944	dotnet/runtime	System.Globalization.Tests.IdnMappingIdnaConformanceTests.GetUnicode_Invalid	#110651
893697	dotnet/runtime	System.Globalization.Tests.IdnMappingIdnaConformanceTests.GetAscii_Invalid	#110651
894059	dotnet/runtime	System.Globalization.Tests.IdnMappingIdnaConformanceTests.GetUnicode_Invalid	#109648
893209	dotnet/runtime	System.Globalization.Tests.IdnMappingIdnaConformanceTests.GetUnicode_Invalid
893212	dotnet/runtime	System.Globalization.Tests.IdnMappingIdnaConformanceTests.GetUnicode_Invalid
888621	dotnet/runtime	System.Globalization.Tests.IdnMappingIdnaConformanceTests.GetUnicode_Invalid	#110492

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
2	5	6

[dotnet-policy-service]

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

[dotnet-policy-service]

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

[jkotas]

@tarekgh It is not ok to use "Known Build Errors" to ignore deterministic failures introduced by the PR. Our goal is to have green CI.

You should disable the failing test against an issue in situations like this instead.

[tarekgh]

@jkotas there is no change in the PR caused the failure. It is because the environment is now using an updated version of ICU which is causing the failure. So, there is no real product problem. We have fixed the test in main but back port the fix failed. I am currently off, if I get a chance soon to log in will try to either port the fix manually or disable the test.