Add Dockerfile using RBE's Jessie base image#15499
Conversation
|
|
There was a problem hiding this comment.
nit: add an explanatory comment what's the image about - the image name is incomprehensible for someone who doesn't have lot of knowledge about foundry/RBE.
There was a problem hiding this comment.
Done in new Dockerfile
There was a problem hiding this comment.
as discussed, let's introduce a separate rbe clang image (cxx_sanitizers.. ) and use cxx_jessie_x64 (after removing clang) for running basic C/C++ suites.
There was a problem hiding this comment.
We actually use the current Jessie Dockerfile for clang3.5. clang3.5 is installed in https://github.com/grpc/grpc/blob/master/tools/dockerfile/test/cxx_jessie_x64/Dockerfile#L73, so we at least have to keep that version of clang, but I'm fine with removing the version installed from source.
Before updating my PR, since I forgot to remove clang, are you ok with the name cxx_rbe_jessie_x64 or do you think cxx_sanitizers_x64 is better?
There was a problem hiding this comment.
I think cxx_sanitizers_... is better because it's more readable. no one knows what rbe is.
|
|
All sanitizers passed except for This was on Clang 6, using an older RBE base, but I will be updating to Clang 7 |
|
|
There was a problem hiding this comment.
can we remove <%include file="../../clang_update.include"/> from this file?
There was a problem hiding this comment.
I think not that many folks know what RBE means -> either add a comment or rename.
There was a problem hiding this comment.
Changed the name of the file
|
|
|
|
|
|
|
|
|
|
|
|
@jtattermusch I think this is ready for review. This PR introduces two ASAN C++ failures, both |
|
| return 'Makefile' | ||
|
|
||
| def _clang_make_options(self, version_suffix=''): | ||
| if self.args.config == 'ubsan': |
There was a problem hiding this comment.
why do we need to special-case ubsan?
There was a problem hiding this comment.
I'm actually not sure why UBSAN is a special case. If anything, I expect all of the sanitizers to break. Before this change, UBSAN wouldn't build from a linking error because it would use clang instead of clang++ as the LD. Our Makefile specifies that the LD for all sanitizers should be clang++, but I'm guessing run_tests.py overrides that behavior.
jtattermusch
left a comment
There was a problem hiding this comment.
LGTM (but please see the comment about special-casing ubsan).
|
|
MacOS failure - #15027 After a master sanitizer build runs all tests, I'll open issues for the new test failures. |
Add a Dockerfile that uses a RBE base image with Clang 7 to run sanitizers.