Skip to content

Run Helix tests on VS2026#65162

Open
wtgodbe wants to merge 6 commits intomainfrom
wtgodbe/Helix2026
Open

Run Helix tests on VS2026#65162
wtgodbe wants to merge 6 commits intomainfrom
wtgodbe/Helix2026

Conversation

@wtgodbe
Copy link
Member

@wtgodbe wtgodbe commented Jan 21, 2026

Counterpart of #65088. VS2026 is the in-support version now

Copilot AI review requested due to automatic review settings January 21, 2026 18:24
@wtgodbe wtgodbe requested review from a team and JamesNK as code owners January 21, 2026 18:24
@github-actions github-actions bot added the area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions label Jan 21, 2026
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 Helix test infrastructure to use VS2026 queue names instead of VS2022, aligning with the fact that VS2026 is now the in-support version. The changes update queue references in both the Helix configuration and test skip attributes.

Changes:

  • Updated Helix queue name from VS2022 to VS2026 in the build configuration
  • Updated SkipOnHelix attributes in IIS and HttpSys tests to reference VS2026 queues

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
eng/targets/Helix.Common.props Updates Windows Helix queue from VS2022.Pre to VS2026.Pre.Scout for PR checks
src/Servers/IIS/IIS/test/Common.LongTests/StartupTests.cs Updates SkipOnHelix queue names from VS2022 to VS2026
src/Servers/HttpSys/test/FunctionalTests/Http2Tests.cs Updates SkipOnHelix queue names from VS2022 to VS2026 (2 occurrences)

wtgodbe and others added 3 commits January 21, 2026 11:51
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@dotnet-policy-service
Copy link
Contributor

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.

@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Jan 29, 2026
@wtgodbe
Copy link
Member Author

wtgodbe commented Feb 3, 2026

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

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

Labels

area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants