Skip to content
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

Update to bazel 8.0.0 #4729

Open
wants to merge 6 commits into
base: trunk
Choose a base branch
from
Open

Conversation

jonmeow
Copy link
Contributor

@jonmeow jonmeow commented Dec 20, 2024

This updates to bazel 8.0.0, also updating bazel mod deps and tools to make that function. The release is a couple weeks old, and we haven't updated in a while, and it's a major release. Note it includes some incompatible flag flips that this is trying to update with respect to. I'll try generally enabling incompatible support separately.

The most visible bazel behavior change here will be the change from ~ to + in repo path names. (If you're curious, bazelbuild/bazel#23127 indicates this fixes a Windows performance issue)

Note that this is building on top of both the action env update in #4728 (which got me started down this path) and the proto removal in #4731 (which would add significant work to this update). Only the commit starting at "Work towards bazel 8.0.0" is specifically part of this PR.

@jonmeow jonmeow changed the title Work towards bazel 8.0.0 Update to bazel 8.0.0 Dec 20, 2024
@jonmeow jonmeow marked this pull request as ready for review December 20, 2024 22:05
@github-actions github-actions bot requested a review from geoffromer December 20, 2024 22:05
@github-actions github-actions bot added documentation An issue or proposed change to our documentation explorer Action items related to Carbon explorer code labels Dec 20, 2024
Copy link
Contributor

@chandlerc chandlerc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Reviewing just last change here)

LG generally, but hopefully can remove one of the workarounds inline...

MODULE.bazel Outdated
Comment on lines 68 to 72
# protobuf and tcmalloc rely on incompatible rules_fuzzing versions. Force the
# protobuf version, even though it's just an indirect dependency of something.
#
# TODO: This is probably okay because of how we use tcmalloc, but it's
# definitely undesirable and should be removed when possible.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove this now that we don't have the protobuf issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed -- I thought I'd still been seeing a conflict but I guess not.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

If one comes up, not a big deal, but good to document whatever is left causing it.

Copy link
Contributor

@chandlerc chandlerc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG (once the dependencies land)

github-merge-queue bot pushed a commit that referenced this pull request Dec 21, 2024
As part of migrating to the latest bazel configurations in #4729, I'm
running into proto toolchain issues. For example:
"Error: <target @@protobuf+//:cc_toolchain> (rule
'proto_lang_toolchain') doesn't contain declared provider
'ProtoLangToolchainInfo'"

Although we may eventually want more use of proto, right now the only
use is for the explorer fuzzer. The explorer codebase is essentially
frozen, so continuing to run it isn't gaining us much (in fact, we've
already disabled autofuzzing for it).

So, rather than trying to fix the proto setup, this change:

1. Deletes `explorer/fuzzing`
2. Removes proto portions of `testing/fuzzing`, which were only in-use
by the explorer
3. Removes some ancillary proto support, which would otherwise break
from the bazel changes and would be difficult to validate as "still
working"

This change is partly isolated in order to make it easier to revive bits
of (3).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation An issue or proposed change to our documentation explorer Action items related to Carbon explorer code infrastructure toolchain
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants