beads' MODULE.bazel registered no C toolchain, so -race and cgo builds used
the autodetected local_config_cc of the machine that ran analysis. From a
client with lld installed (cherry) every remote cgo/-race link failed with
"collect2: fatal error: cannot find 'ld'" (the workers have no lld), and the
host gcc path, lld availability and gcc-version inputs keyed every Go action
to the client machine.
Port gastownhall/gascity's design:
- toolchains_llvm 1.11.0 with a pinned LLVM 22.1.8 slice
(third_party/cc_toolchain/llvm_dist.bzl) and a sysroot of sha256-pinned
Ubuntu 24.04 debs (deb_sysroot.bzl), without ICU (ICU policy);
stock toolchains_llvm LLVM on other hosts.
- .bazelrc: BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1 so nothing falls back to the
host compiler.
- //platforms:rbe_worker, selected unconditionally, whose worker-env exec
property is the sha256 of tools/rbe/worker-env.txt (a copy of the shared
rbe-west OSS pool's manifest, owned by gascity), so the worker host is in
every action key.
- scripts/bazel_hermetic_cc_test.go and scripts/rbe_worker_env_test.go guard
both.
Refs: ga-96smfk.20
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>