Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Dec 10, 2025

main PR #122371

Description

Updates OpenSUSE container version from 15.6 to 16.0 in Helix pipeline configuration for Linux x64 CoreCLR extra-platforms testing, and includes necessary test fixes to ensure compatibility with OpenSUSE 16.0.

Infrastructure Changes:

  • eng/pipelines/libraries/helix-queues-setup.yml: Updated queue name and container image from openSUSE.15.6 to openSUSE.16.0

Test Compatibility Fixes (backported from main PR #122371):

  1. Platform Detection: Added IsOpenSUSE16 property to PlatformDetection.Unix.cs to detect OpenSUSE 16.0 and OpenSUSE Leap 16.0

  2. Networking Tests: Added ActiveIssue attribute to skip Package_Unsupported_NTLM test on OpenSUSE 16, which ships with broken gss-ntlmssp 1.2 (similar to Ubuntu 24 and 26)

  3. Globalization Tests:

    • Added Unicode 17.0 IDNA test data and test infrastructure for ICU 78+ compatibility
    • Updated test data factory to use appropriate Unicode version based on ICU version

Note: Japanese calendar changes were intentionally excluded from this PR as they constitute a breaking change that requires servicing approval. The existing test fix from commit ff082da is sufficient for OpenSUSE 16.0 compatibility.

Customer Impact

None. Infrastructure-only change for CI/CD pipeline testing with test compatibility fixes to ensure test suite passes on the new platform.

Regression

No. This is a container version update to align with current OpenSUSE releases, with corresponding test fixes to handle platform-specific behavior differences.

Testing

CI/CD pipeline validation through runtime-extra-platforms workflow. Test fixes ensure that the existing test suite works correctly on OpenSUSE 16.0 by:

  • Skipping tests that fail due to known platform limitations
  • Updating test data to match newer ICU versions

Risk

Low. Changes include:

  1. Single line container version reference update in pipeline configuration
  2. Platform-specific test skips and data updates that don't affect runtime behavior
  3. All changes are test-only fixes that ensure compatibility without modifying production code
  4. Japanese calendar breaking changes were reverted to maintain servicing policy compliance

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

Original prompt

Please update opensuse container references to 16.0, such as in this file https://github.com/dotnet/runtime/blob/release/10.0/eng/pipelines/libraries/helix-queues-setup.yml


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

@richlander richlander changed the title [WIP] Update openSUSE container references to 16.0 [release/10.0] Update openSUSE container references to 16.0 Dec 10, 2025
@dotnet-policy-service
Copy link
Contributor

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

Co-authored-by: richlander <2608468+richlander@users.noreply.github.com>
Copilot AI changed the title [release/10.0] Update openSUSE container references to 16.0 Update OpenSUSE container references to 16.0 Dec 10, 2025
Copilot AI requested a review from richlander December 10, 2025 01:00
@richlander richlander marked this pull request as ready for review December 10, 2025 23:24
Copilot AI review requested due to automatic review settings December 10, 2025 23:24
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the OpenSUSE container reference in Helix pipeline configuration from version 15.6 to 16.0 to align with current OpenSUSE releases. This is an infrastructure-only change for CI/CD testing pipelines.

Key changes:

  • Updated Helix queue name and container image references from OpenSUSE 15.6 to 16.0
  • Change applies to Linux x64 CoreCLR extra-platforms inner loop testing

@richlander
Copy link
Member

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@richlander
Copy link
Member

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jeffhandley
Copy link
Member

/ba-g Failures are related to macOS 13 deprecation and unrelated

@richlander
Copy link
Member

It looks like runtime-extra-platforms never ran so we don't ahve the required coverage. Kicking off again.

Copilot AI changed the title [release/10.0] Update OpenSUSE container references to 16.0 [release/10.0] Update OpenSUSE container references to 16.0 and add test compatibility fixes Jan 22, 2026
@richlander
Copy link
Member

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@richlander
Copy link
Member

This change appears clean to me. PTAL @wfurt @tarekgh.

@tarekgh
Copy link
Member

tarekgh commented Jan 22, 2026

@richlander I am seeing you have ported the Japanese calendar breaking change here. I don't think this is right. If we need to service this change need to be approved by tactics. So far, I am not seeing any real user need it or blocked by this change to justify porting to servicing. I already submitted before in this PR the change ff082da which make the tests pass.

@richlander
Copy link
Member

richlander commented Jan 22, 2026

Oh, got it. We can revert that part. Do you want to ask copilot to make the desired change? Sorry that I misinterpreted your earlier statement.

That said, I have a memory (from yesterday; perhaps wrong) that a rebuild still demonstrated the calendar related failure.

@tarekgh
Copy link
Member

tarekgh commented Jan 22, 2026

@copilot could you please revert the changes done in the files: JapaneseCalendar.cs, JapaneseCalendar.Icu.cs, JapaneseCalendarAddMonths.cs, and JapaneseCalendarTests.cs

@tarekgh
Copy link
Member

tarekgh commented Jan 22, 2026

That said, I have a memory (from yesterday; perhaps wrong) that a rebuild still demonstrated the calendar related failure.

Let's see if we get any failure after reverting the changes and I can try to fix that.

Reverted changes to Japanese calendar minimum date as this is a breaking change that should not be ported to servicing without approval. The test fix from commit ff082da is sufficient for OpenSUSE 16.0 compatibility.

Files reverted:
- JapaneseCalendar.cs
- JapaneseCalendar.Icu.cs
- JapaneseCalendarAddMonths.cs
- JapaneseCalendarTests.cs

Co-authored-by: tarekgh <10833894+tarekgh@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Jan 22, 2026

@copilot could you please revert the changes done in the files: JapaneseCalendar.cs, JapaneseCalendar.Icu.cs, JapaneseCalendarAddMonths.cs, and JapaneseCalendarTests.cs

Done. Reverted the Japanese calendar changes in commit f19d642. The files have been restored to their original state (with the 1868/09/08 minimum date). The test fix from commit ff082da should be sufficient for OpenSUSE 16.0 compatibility without the breaking change.

Copilot AI requested a review from tarekgh January 22, 2026 17:23
@tarekgh
Copy link
Member

tarekgh commented Jan 22, 2026

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@richlander
Copy link
Member

@tarekgh I see the Japanese Calendar failures.

@tarekgh
Copy link
Member

tarekgh commented Jan 22, 2026

@richlander I have no idea why these failed calendar tests are listed under known test errors and pointing at #117164. Anyway, I'll try to take a look tomorrow and find out what is going on.

@tarekgh
Copy link
Member

tarekgh commented Jan 23, 2026

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-Infrastructure NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) Servicing-approved Approved for servicing release

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

6 participants