-
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
Step 2: Bump bazel 3.7.2 in envoy build tree #14134
Step 2: Bump bazel 3.7.2 in envoy build tree #14134
Conversation
There was an erroneous commit in the original PR, note this is also draft in anticipation of 3.7.1 with a significant hash WIP |
bazel/repository_locations.bzl
Outdated
@@ -25,7 +25,8 @@ REPOSITORY_LOCATIONS_SPEC = dict( | |||
project_name = "bazel-toolchains", | |||
project_desc = "Bazel toolchain configs for RBE", | |||
project_url = "https://github.com/bazelbuild/bazel-toolchains", | |||
version = "3.6.0", | |||
version = "3.7.1", | |||
# TBD, not here yet |
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.
Raised an inquiry at bazelbuild/bazel#12188 (comment) since this hasn't shown up yet, the day after the 3.7.1 bazel release.
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.
Version 3.7.0 which exists already should be usable with Bazel 3.7.x
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.
Versions 3.7.0 and 3.7.1 both had build time regressions in envoy.
Version 3.7.0 and earlier entirely failed to invoke bazel on Windows when bazel would discover llvm 11.0.0 (earlier llvm 10 flavors were not an issue.)
The bazel 3.7.2 release solves both of these issues, based on initial review of rc1.
3.7.x won't be usable unless we get bazelbuild/bazel#12545 fix cherry-picked |
This is required for Windows clang-cl - Identify toolchain 3.7.1 with the necessary clang-cl 11.0.0 windows fix - Identify bazel 3.7.2 with regression fix to fuzz tests Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Temporary condition just to review CI ahead of 3.7.2 release Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Should be good to go once envoyproxy/envoy-build-tools#114 is merged and has generated bazel 3.7.2 docker images |
@wrowe toolchains are generated |
/retest |
Retrying Azure Pipelines: |
/retest CodeQL-Build |
Retrying Azure Pipelines: |
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
@wrowe you'll have to update envoy-build-tools SHA as well |
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Not 100% certain this is correct, but need to provision docker locally for verification Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
This looks promising, TY @sunjayBhatia |
Failure is in the flaky test reporting script from some quick googles, looks like an issue caused by us updating to python 3.9 :( similar issue: https://stackoverflow.com/questions/64497319/python-discord-py-error-could-not-build-wheels-for-multidict-yarl-which-use |
New versions needed with updated wheels for python 3.9 Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
Required a bump to some dependencies for python 3.9 |
/retest |
Retrying Azure Pipelines: |
macos is same failure as on |
@lizan or @envoyproxy/dependency-shepherds this is ready for a stamp of approval. No action here needed for the macos test, as noted above. |
I have a fix for OSX CI here: #14515 |
Merge main and OSX should be fixed. /wait |
Let's see if this clears macOS Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
/retest to clear fuzz flakiness obstacle in |
Retrying Azure Pipelines: |
I'm at a loss... and my connectivity today is almost entirely useless. @htuch you are on-point because moving to clang-cl is your ask. @mattklein123 or @sunjayBhatia do you see what the issue is with the fuzz test pipeline? |
Pinging @lizan in case you have the solution to the fuzz test pipeline. |
https://dev.azure.com/cncf/4684fb3d-0389-4e0b-8251-221942316e06/_apis/build/builds/62461/logs/223 |
I saw the coverage timeout on a different PR so probably unrelated but I'm not sure. cc @asraa |
Let's go ahead and /retest |
Retrying Azure Pipelines: |
That's what I saw, @sunjayBhatia, but I'm unclear whether this change influences it. Since Matt has seen it elsewhere, I suspect this PR is ready to merge. |
Ok, the bug is cleared, @envoyproxy/dependency-shepherds we need your response, this is now a month overdue. |
Commit Message: Bump bazel 3.7.2
Additional Description:
Build using 3.7.2 bazel to resolve bazel regression described in issue 12545
Build using 3.7.1-based bazel-toolchain for windows llvm 11.0.0 compatibility
Bump ci/flaky_test/requirements.txt to avoid python 3.9.x issues
Risk Level: low (bazel is observing semver)
Testing: local (in draft, as RC's)
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a