Skip to content

Conversation

@richlander
Copy link
Member

@richlander richlander commented May 13, 2025

Related:

Pipeline and Test Queue Modernization:

  • Updated pipeline YAML files to use newer container images for CentOS Stream 9, AlmaLinux 9, Alpine 3.22, and AzureLinux 3, and modernized queue names for several Linux distributions.
  • Adjusted test queue logic to better differentiate between "extra platforms" and standard runs, and to align with new image and queue naming conventions.

Supporting Changes:

Copilot AI review requested due to automatic review settings May 13, 2025 00:30

This comment was marked as outdated.

@richlander
Copy link
Member Author

/azp run runtime-libraries-coreclr outerloop-linux

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@richlander
Copy link
Member Author

/azp run runtime-libraries-coreclr outerloop-linux

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@richlander
Copy link
Member Author

These failures all look existing.

@carlossanlop

Copy link
Member

@mthalman mthalman left a comment

Choose a reason for hiding this comment

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

@richlander
Copy link
Member Author

/azp run runtime-libraries-coreclr outerloop-linux

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@richlander
Copy link
Member Author

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@PranavSenthilnathan PranavSenthilnathan added the Servicing-consider Issue for next servicing release review label Oct 14, 2025
@richlander
Copy link
Member Author

/ba-g "Existing issues"

This looks good. I see the same failures in #120516.

@richlander richlander enabled auto-merge (squash) October 15, 2025 22:48
@jeffhandley jeffhandley requested a review from artl93 October 16, 2025 23:56
@jeffhandley
Copy link
Member

@artl93 This is ready for your review. The failing tests are unrelated and Build Analysis is green. I believe this should be treated as Tell Mode, but I defer to you if you want it to go through Tactics for approval or approve it yourself.

This will now use newer container images for CentOS Stream 9, AlmaLinux 9, Alpine 3.22, and Azure Linux 3 in our .NET 8 servicing pipelines. Azure Linux 3 libraries coverage is included without needing to use extra-platforms.

artl93 pushed a commit that referenced this pull request Oct 30, 2025
Backport of #117694 to release/9.0-staging

/cc @jeffhandley @wfurt @ManickaP 

## Customer Impact

Related to #115502. Default AZL has firewall that blocks multicast. 

- [ ] Customer reported
- [x] Found internally

## Regression

- [ ] Yes
- [x] No

## Testing

This was verified in main and is also being backported to
release/8.0-staging via #115502, to ensure the test doesn't fail in our
baseline extra-platforms tests.

## Risk

Low. Conditional test disablement.

---------

Co-authored-by: wfurt <[email protected]>
Co-authored-by: Marie Píchová <[email protected]>
@rbhanda rbhanda added this to the 8.0.23 milestone Nov 20, 2025
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Nov 20, 2025
@richlander
Copy link
Member Author

Hey @wfurt ... I see #122155. Please continue with that. I can handle merge conflicts here. That said, it looks like networking failures are a primary issue with the latest changes I made. It would be good to resolve those in one of the PRs.

@wfurt
Copy link
Member

wfurt commented Dec 4, 2025

For the System.Net.NetworkInformation.Functional.Tests we need to pick up #120736. It seems like it was ported back to 9.0 and 10.0 but not here. cc: @rzikm

@wfurt
Copy link
Member

wfurt commented Dec 4, 2025

And the System.Net.Quic.Functional.Tests seems the same. It uses NetworkInfo to monitor changes and also fails on unspeakable file.

@rzikm
Copy link
Member

rzikm commented Dec 4, 2025

#122188

@wfurt
Copy link
Member

wfurt commented Dec 4, 2025

#122188

do we skip the 8.0-staging now?

@jozkee
Copy link
Member

jozkee commented Dec 5, 2025

do we skip the 8.0-staging now?

No, please keep using it for 8 and 9 servicing. Since #122188 is already in base 8.0, you can simply mention it nex to the ba-g if the lack of the fix is blocking you.

@jozkee
Copy link
Member

jozkee commented Dec 5, 2025

FYI, I see the milestone for 8.0.23, it would be nice to get this merged before 4:00 PM PST; otherwise, you will need to retarget to release/8.0.

@richlander richlander merged commit 2118a1a into dotnet:release/8.0-staging Dec 5, 2025
179 checks passed
@richlander richlander deleted the 8.0-staging-ci-update branch December 5, 2025 20:09
MihaZupan added a commit that referenced this pull request Dec 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.