-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
use clang 12 #18220
use clang 12 #18220
Conversation
c7a2500
to
dbc0919
Compare
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
dbc0919
to
8ad8a2d
Compare
Can we bump the Clang version at https://github.com/envoyproxy/envoy/blob/main/bazel/repository_locations.bzl#L902-L916 for consistency? |
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
It would be preferable to not introduce a patch. Since we control |
@moderation this is just a draft to test how this goes in CI, will see what will be the path forward. |
Coverage dip maybe due to tooling change? We can adjust the levels for now. @alyssawilk |
Yes I think coverage dip is due to they change how lines get counted. I will dig it later. |
If we need to bump we need to bump. The problem is that it looks like it's now considering comments to be code. It'd be lovely to fix if we can see 115 for |
This is an improvement? The main branch shows comments to be code and PR doesn't count that. |
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
yep, was reading it backwards. |
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
/retest |
Retrying Azure Pipelines: |
@htuch @moderation this is ready to go, about patches: rules_cc patch posted to bazelbuild/rules_cc#115 |
I can work with the RBE dev to make this aspect of toolchain generator configurable. Once this is done we can update toolchain generator. I see this patch as temporary. |
/lgtm deps |
…s caused by envoyproxy/envoy#18220 updating the run_bazel_coverage_script.sh Signed-off-by: Luis Fernando Pino Duque <luis@engflow.com>
hey, did we envoy-dev announce this change? we should warn folks to install clang 12 no? Lizan if this makes sense can you do that? |
AIUI, the build tools are bumped to 12. The flags we've changed should keep clang-11 users largely compatible, there's nothing revolutionary in this change, so they should still be able to build locally with clang-11 except very specific platforms. |
* main: (114 commits) kafka: add header support to mesh-filter (envoyproxy#18248) rbac: add support for upstream ip policy. (envoyproxy#17645) SIPProxy BUGFIX UT failure for fastbuild/debug (envoyproxy#18303) quic: updating goaway code (envoyproxy#18291) various tiny fixes (envoyproxy#18287) dns cache: remove assert at this layer (envoyproxy#18301) [ext_authz]: ext_authz filter unit test that use real threading (envoyproxy#17742) signal action: fully disable sigaltstack on Apple (envoyproxy#18299) Add missing dependencies (envoyproxy#18297) ext_proc: Pass stream_info to gRPC streams (envoyproxy#18190) use clang 12 (envoyproxy#18220) Update PR template to include the "Fixes commit" message when reverting or fixing bad commits (envoyproxy#18298) [test] Fixing integration test to cleanup cleanly (envoyproxy#18293) test: moving grpc bridge tests out of core directory (envoyproxy#18227) runtime: disable deprecated extensions names by default (envoyproxy#18239) quiche: updating deps (envoyproxy#18272) sip_proxy: SIP protocol support in envoy (envoyproxy#18039) http: add core retry policy to route retry policy conversion utility (envoyproxy#17803) build: updating stale visibility (envoyproxy#18278) alternate_protocols_cache: Impose a max size limit on the alternate protocols cache (envoyproxy#18258) ... Signed-off-by: Michael Puncel <mpuncel@squareup.com>
map<string, JwtRequirement> | ||
requires = 3; |
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.
I wonder if this change was accidental. FORCE_PROTO_FORMAT=yes ./tools/proto_format/proto_format.sh check
complains about this.
(same applies to corresponding v3/config.proto)
Signed-off-by: Lizan Zhou lizan@tetrate.io