-
Notifications
You must be signed in to change notification settings - Fork 5.1k
[release/6.0] [HTTP/3] Fixed stress #60723
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsManual backport of #60364 to release/6.0 This is a test-only change updating msquic for HttpStress so we can run linux tests again on Customer ImpactWe need stress tests to assure the quality of the HTTP stack in .NET 6.0. TestingCI run should show if the build error is gone. RiskNone.
|
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, you're faster than me.
@danmoseley @karelz we need to merge this and #60682 before 6.0 GA 4pm PST Friday! |
If this is test-only is it required for GA? |
I agree that 6.0 servicing should be sufficient - whichever is easier for 6.0 shipping. |
Does'nt need servicing-consider as it's test/infra work. It does need to wait for branch to open that's all |
Removing NO MERGE, as it now can be merged. |
@danmoseley ping? |
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
Thanks for the clarification. I will then merge regardless of the status of that build. |
Manual backport of #60364 to release/6.0
This is a test-only change updating msquic for HttpStress so we can run linux tests again on
release/6.0
./cc @ManickaP
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.