-
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
bazel: update to v5.0.0 #19706
bazel: update to v5.0.0 #19706
Conversation
CC @envoyproxy/dependency-shepherds: Your approval is needed for changes made to |
just tracking through trying to figure the couple of errors one is the same error that @keith hit previously #18718 (comment) the other is a problem with it not finding |
im not certain - but i think that envoyproxy/envoy-build-tools#161 can fix the ld problem |
@htuch @adisuissa @keith it looks like the only remaining blocker to upgrading to bazel 5 is the pgv issue Not sure exactly why but it cant find the compiled protobuf files
any clues on this one ? |
Signed-off-by: Faseela K <faseela.k@est.tech>
Signed-off-by: Faseela K <faseela.k@est.tech>
Signed-off-by: Faseela K <faseela.k@est.tech>
Signed-off-by: Faseela K <faseela.k@est.tech>
Signed-off-by: Faseela K <faseela.k@est.tech>
Signed-off-by: Faseela K <faseela.k@est.tech>
Signed-off-by: Faseela K <faseela.k@est.tech>
405fa82
to
2353f22
Compare
re the pgv/api errors, and on the basis that the fail seems only to occur in CI, im guessing that the it must be RBE/toolchain related at the same time the fail was happening before we upgraded the toolchains, so it seems to be something related to how bazel 5 loads external deps (for RBE) |
Can we try disabling remote execution for this CI job / action specifically, I bet this is this issue: bazelbuild/bazel#13819 |
For just this test we could add |
the issue looks correct in terms of symptoms, but we werent having this problem before bazel 5 and that ticket has been around a while, and refers to 4.1, so im wondering what changed that made it no longer work |
Yea good question, there are some open fixes for it though, so hopefully we won't have to live with any workaround for long |
Signed-off-by: Faseela K <faseela.k@est.tech>
Signed-off-by: Faseela K <faseela.k@est.tech>
Signed-off-by: Faseela K <faseela.k@est.tech>
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.
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.
LGTM. Landing it. We have the entire week to sort out any collateral dmg.
Great work, thanks for doing this! |
* bazel: update to v5.0.0 * Updated envoy-build-tools dependency * Removed envoy_build_tools.patch * Fixed java runtime version flag * Fixed gcc test * Remove outdated java flags * Workaround attempt for test failures * Incorporate review comments Signed-off-by: Faseela K <faseela.k@est.tech> Signed-off-by: Josh Perry <josh.perry@mx.com>
* bazel: update to v5.0.0 * Updated envoy-build-tools dependency * Removed envoy_build_tools.patch * Fixed java runtime version flag * Fixed gcc test * Remove outdated java flags * Workaround attempt for test failures * Incorporate review comments Signed-off-by: Faseela K <faseela.k@est.tech> Signed-off-by: Ryan Northey <ryan@synca.io>
* bazel: update to v5.0.0 * Updated envoy-build-tools dependency * Removed envoy_build_tools.patch * Fixed java runtime version flag * Fixed gcc test * Remove outdated java flags * Workaround attempt for test failures * Incorporate review comments Signed-off-by: Faseela K <faseela.k@est.tech> Signed-off-by: Ryan Northey <ryan@synca.io>
#18718
Depends on envoyproxy/envoy-build-tools#157
Signed-off-by: Faseela K faseela.k@est.tech