-
Notifications
You must be signed in to change notification settings - Fork 5.2k
HttpStress do not use SYS_PTRACE cap for docker runs #76307
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
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsAccording to an offline discussion with engineering folks, there is no need for SYS_PTRACE on newer Linux kernels, so we can remove it for all platforms. The PR is marked as draft because it contains an emulated crash to test dump creation. If everything works fine, I will remove it. Fixes #76045
|
This reverts commit 8cdfad5.
The artifacts zip-s contain empty folders even after my undo commit 956e887: I think we should go ahead with the capability removal and investigate the artifact creation issues later. |
This reverts commit 48bfd4a.
This comment was marked as resolved.
This comment was marked as resolved.
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.
Thanks!
/azp run runtime-libraries stress-http |
Azure Pipelines successfully started running 1 pipeline(s). |
/backport to release/7.0 |
Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3267925204 |
According to an offline discussion with engineering folks, there is no need for SYS_PTRACE on newer Linux kernels, so we can remove it for all platforms.
The PR is marked as draft because
it contains an emulated crash to test dump creation. If everything works fine, I will remove it.Fixes #76045