[release/7.0] HttpStress do not use SYS_PTRACE cap for docker runs #77125
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
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. |
@carlossanlop oops I missed this little advice 😆 Should be good to go now! |
ghost
locked as resolved and limited conversation to collaborators
Backport of #76307 to release/7.0
/cc @antonfirsov
Customer Impact
This is a test-only change fixing an optional pipeline. Nightly
stress-httpruns are important for QA of the networking stack.Testing
N/A
Risk
None