[release/6.0] <EnablePreviewFeatures> for HttpStress

[github-actions]

Backport of #59410 to release/6.0

/cc @antonfirsov

This is a test-only change fixing a build error in HttpStress so we can run stress tests again on release/6.0.

Example failing build on the release/6.0 branch:
https://dev.azure.com/dnceng/public/_build/results?buildId=1429667&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=8ca65746-3bfa-57bf-9141-d805b5d39db5

Customer Impact

We need stress tests to assure the quality of the HTTP stack in .NET 6.0.

Testing

CI run should show if the build error is gone.

Risk

None.

[ghost]

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

Issue Details

---

Backport of #59410 to release/6.0

/cc @antonfirsov

Customer Impact

Testing

Risk

Author:	github-actions[bot]
Assignees:	-
Labels:	area-System.Net.Http
Milestone:	-

[antonfirsov]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[danmoseley]

@antonfirsov no special approval required to commit this. However, there's a cut off in this branch for 6.0 GA at 4pm PST Friday. After that the branch likely needs to hold all changes for a bit.

[antonfirsov]

However, there's a cut off in this branch for 6.0 GA at 4pm PST Friday. After that the branch likely needs to hold all changes for a bit.

@danmoseley In that case it would be really important to merge this and #60723 before that deadline. Latter PR still needs approval. Unfortunately I don't have rights to merge into this branch. Can you help me by pinging someone who can do the merge? after the approval of #60723, which will likely happen tomorrow during Prague working hours EDIT: done
-- #60723 (review).

[danmoseley]

@antonfirsov would it make sense to just hold this and the other one until the branch opens again for 6.0.1, next month? If it's just enabling more testing, and won't make the last build tomorrow any better?

We'll no doubt be taking changes into this branch for tests and such things for the full 3 years that 6.0 will be in support. tomorrow is just the cutoff for 6.0.0.

[danmoseley]

Let's wait until branch opens for 6.0.1

If you need to do stress testing eg of the latest msquic please do so in main or locally until then

[karelz]

Removing NO MERGE as it is now ready for merge into 6.0 servicing.

@danmoseley does it need Approval label to be merged? Or how does it work for test-only changes?

[antonfirsov]

@karelz did you close this on purpose? Is there something that prevents us merging this?

[karelz]

Nope, that was a mistake, sorry and thanks for catching it.

[karelz]

@danmoseley ping?

[danmoseley]

Oops, missed this. No approval needed for test-only changes. As long as the branch is open.

[antonfirsov]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[antonfirsov]

@danmoseley what is the process for getting this and #60723 merged? Should we apply some label, or ping some people? Note that both PR-s are needed to fully fix stress runs.

[danmoseley]

Just ask @safern whether branch is open and he can merge it. Or else I can.

[safern]

The branch doesn't open until around December 17th once the branding changes are open. If this is approved we can add servicing-approved label and I'll handle the merge once the branch is open.

[safern]

If this is approved we can add servicing-approved label and I'll handle the merge once the branch is open.

Ah this is a test only change. I'll merge it once the branch is open.

[antonfirsov]

@safern thanks! Is there a way to put a reminder on both this PR and #60723 to make sure they get merged? Maybe apply servicing-approved regardless?

[safern]

I will look at all PRs based on target branch and milestone, so no worries, it will get merged.