Uh oh!
There was an error while loading. Please reload this page.
[release/6.0] [HTTP/3] Fixed stress - #60723
Conversation
ghost
commented
Oct 21, 2021
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.
|
antonfirsov
commented
Oct 21, 2021
/azp run runtime-libraries stress-http |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ManickaP
left a comment
There was a problem hiding this comment.
Thanks, you're faster than me.
antonfirsov
commented
Oct 21, 2021
@danmoseley@karelz we need to merge this and #60682 before 6.0 GA 4pm PST Friday! |
mmitche
commented
Oct 21, 2021
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. |
danmoseley
commented
Oct 28, 2021
Does'nt need servicing-consider as it's test/infra work. It does need to wait for branch to open that's all |
karelz
commented
Nov 22, 2021
Removing NO MERGE, as it now can be merged. |
karelz
commented
Nov 30, 2021
@danmoseley ping? |
safern
commented
Dec 15, 2021
/azp run runtime-libraries stress-http |
|
Azure Pipelines successfully started running 1 pipeline(s). |
safern
commented
Dec 15, 2021
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.