-
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
build: Bump Bazel to 3.7.0 #14123
build: Bump Bazel to 3.7.0 #14123
Conversation
Signed-off-by: Sunjay Bhatia <[email protected]>
/lgtm deps |
coverage differences in |
I've seen same in different PR as well, might not related to the bump but might be some flakes (and being cached) |
@sunjayBhatia is taking the entire week, but I'm available to tweak commits, or you can do so yourself. My 2c, let's take this if it is convenient before Tuesday, just to have greater confidence in the 3.7.1 bump. |
all fuzz_coverage tests are failing and it's obviously broken, so we need to fix that and I don't think it will be fixed in 3.7.1 either. |
Have you identified this as bazel's or envoy's defect, @lizan? There's still a window today to note the regression at bazelbuild/bazel#12188 if this represents a 3.6.0 regression. |
Bumps to Bazel 3.7+ are blocked on bazelbuild/bazel#12545 |
closing in favor of #14134, though we will need a 3.7.2 to fix the regression reported in bazelbuild/bazel#12545 |
Commit Message: Bump Bazel to 3.7.0
Additional Description: Build container bumps MSVC toolchain for Windows, helps us move forward to enable clang-cl which requires LLVM 11.0.0 (requires a bug fix backported to Bazel 3.7.1 and in 4.0.0)
Risk Level: Low
Testing: N/A
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A