bazel: remove version warnings #24660
Merged
+2,074
−1,477
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To remove an annoying warning spam logging message.
To remove some warning logging
rockwotj
requested review from
twmb,
r-vasquez,
gene-redpanda and
Deflaimun
as code owners
So they are the same and bazel stops complaining
To match RPK and get rid of annoying warnings in Bazel
rockwotj
force-pushed
the
bazel-warnings
branch
from
ed1a7b5 to
690b6f5
Compare
|
Force push: run |
CI test resultstest results on build#60162
|
|
The only failure is the raft reconfiguration unit test, which is a known flake (and I will soon make logs accessible) |
r-vasquez
approved these changes
Jan 2, 2025
rockwotj
added a commit
that referenced
this pull request
Jan 2, 2025
bazel: remove version warnings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This removes all the annoying warning logging when invoking bazel. Mostly these are due to version mismatches and we just ratchet everything forward.
Backports Required
Release Notes