Skip to content
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

[HttpStress] Consider adding a nightly HTTP/3.0 leg with standard Release MSQUIC build #100529

Open
antonfirsov opened this issue Apr 2, 2024 · 2 comments

Comments

@antonfirsov
Copy link
Member

Besides enabling ASan, #100023 switched to DEBUG msquic, slowing down the runs 2x which which means timing characteristics of the SUT are now quite different. IMO we need to make sure we do stress test the same system as we deploy, therefore I recommend adding another leg to the nightly builds. @ManickaP @radkz @CarnaViire I leave it to you to triage, hopefully I will be able to contribute this change at some point, shouldn't be hard.

Copy link
Contributor

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

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Apr 2, 2024
@ManickaP
Copy link
Member

ManickaP commented Apr 2, 2024

Triage: fine with me. We want results in reasonable time on PRs, but the nightly build can take a bit longer.

@ManickaP ManickaP removed the untriaged New issue has not been triaged by the area owner label Apr 2, 2024
@ManickaP ManickaP added this to the Future milestone Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants