-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[release/6.0] [HTTP/3] Stress disable offending op causing server errors #58541
Conversation
Tagging subscribers to this area: @dotnet/ncl |
Test failures:
|
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
cc @danmoseley |
approved - test stability changes only - if CI passes, anyway. |
Just FYI, even though runtime-libraries stress-http pipeline is red, it's OK to merge. I checked the details of the run and the results correspond to the state we have in main. There are some errors in H/3 stress, but they are vastly reduced. |
@danmoseley this is ready for merge as described above by @ManickaP (the stress in CI is considered passing despite the red cross there at stress) |
Backport of #58442 to release/6.0
Re-enables HTTP stress scenarios that were broken by Kestrel (it's fixed now). Disables 100 Continue operation for HTTP/3 (not yet implemented by Kestrel) which highly improved stability of H/3 stress.
See #58110 (comment)
Contributes to #56310
Fixes #55261
/cc @ManickaP
Customer Impact
Improves HTTP stress coverage and stability.
Testing
Stress test runs in CI / locally.
Risk
Low. This is a test infra change impacting NCL stress test runs only.