-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Flag docker invocations as --privileged on CI #43536
Conversation
r? @aidanhs |
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
src/ci/docker/run.sh
Outdated
@@ -82,6 +82,7 @@ exec docker \ | |||
--env TRAVIS_BRANCH \ | |||
--volume "$HOME/.cargo:/cargo" \ | |||
--volume "$HOME/rustsrc:$HOME/rustsrc" \ | |||
--privileged \ |
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.
Maybe add a comment, why this is needed? It's in the commit message, but it would be more visible here.
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.
Certainly, added!
When upgrading to LLVM 5.0 it was found that the leak sanitizer tests were failing with fatal errors, but they were passing locally when run. Turns out it looks like they may be using new ptrace-like syscalls so the docker container now needs `--privileged` when executing to complete the test.
@bors r+ |
📌 Commit b121689 has been approved by |
@bors rollup |
Flag docker invocations as --privileged on CI When upgrading to LLVM 5.0 it was found that the leak sanitizer tests were failing with fatal errors, but they were passing locally when run. Turns out it looks like they may be using new ptrace-like syscalls so the docker container now needs `--privileged` when executing to complete the test.
When upgrading to LLVM 5.0 it was found that the leak sanitizer tests were
failing with fatal errors, but they were passing locally when run. Turns out it
looks like they may be using new ptrace-like syscalls so the docker container
now needs
--privileged
when executing to complete the test.