-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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/7.0] HttpStress do not use SYS_PTRACE cap for docker runs #77125
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBackport of #76307 to release/7.0 /cc @antonfirsov Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
@carlossanlop can we get this merged if the Windows bits of the |
Test-only, sure, I can merge it as tell-mode (no Tactics approval required). If we're confident stress-http is the only queue needed, we can wait for that check. Ping me when it's done. Don't forget to provide a code review sign-off. |
Test failures are #74838. |
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.
LGTM
@carlossanlop oops I missed this little advice 😆 Should be good to go now! |
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.
Branch is open for merging servicing changes. Failures were all unrelated. Ready to merge.
Backport of #76307 to release/7.0
/cc @antonfirsov
Customer Impact
This is a test-only change fixing an optional pipeline. Nightly
stress-http
runs are important for QA of the networking stack.Testing
N/A
Risk
None