Skip to content

MODULE.bazel: mark test/toolchain deps as dev_dependency - #67

Merged
jayakasadev merged 1 commit into
mainfrom
bazel-dev-deps
Jun 12, 2026
Merged

jayakasadev merged 1 commit into
mainfrom
bazel-dev-deps

Conversation

@jayakasadev

Copy link
Copy Markdown
Owner

What

Mark fuzztest + googletest + the rules_rust toolchain extension as dev_dependency = True in MODULE.bazel. Drop register_toolchains("@rust_toolchains//:all").

Why

  • fuzztest + googletest: only consumed by snmalloc's own C++ tests. As non-dev deps every downstream bzlmod consumer transitively pulled them. fuzztest in particular drags rules_go in, whose cgo.bzl references a CcInfo symbol removed in modern rules_cc — breaks any modern bzlmod project that uses snmalloc as a dep.
  • rust toolchain extension + register_toolchains: only needed for snmalloc's own bazel test //snmalloc-rs/.... As a non-dev registration it would silently overlay a downstream consumer's own toolchain pin.

Cost

Snmalloc's own Rust dev/CI loop now needs --extra_toolchains=@rust_toolchains//:all (e.g. in .bazelrc) since register_toolchains was removed. Not added in this PR.

Evidence

Diff is MODULE.bazel only.

fuzztest + googletest are only consumed by snmalloc's own C++ tests.
Marking them dev keeps them out of downstream resolution — fuzztest
otherwise drags rules_go in, whose cgo.bzl references a CcInfo symbol
removed in modern rules_cc and breaks any bzlmod consumer.

The rules_rust toolchain extension is likewise dev-only — downstream
workspaces pin their own toolchain and a transitive registration here
would silently overlay it.
@jayakasadev
jayakasadev merged commit 6f49b4e into main Jun 12, 2026
34 of 211 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant