Restore exec flag propagation barrier
Allowlists the rust nightly toolchain configuration to ensure that also
affects the exec platform.
Change-Id: Ie146303d6261fdc332debdb0e053a7bfe58fe0c2
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/maize/+/260258
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Erik Gilling <konkers@google.com>
Reviewed-by: Ted Pudlik <tpudlik@google.com>
Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com>
Pigweed-Auto-Submit: Armando Montanez <amontanez@google.com>
diff --git a/.bazelrc b/.bazelrc
index 4a66508..b54da56 100644
--- a/.bazelrc
+++ b/.bazelrc
@@ -33,6 +33,9 @@
# TODO - konkers: fix upstream stable toolchains
common --@rules_rust//rust/toolchain/channel=nightly
+# Ensure this flag is propagated to exec config.
+common --experimental_propagate_custom_flag=@rules_rust//rust/toolchain/channel
+
common --@pigweed//pw_log/rust:pw_log_backend=//subsys/console:pw_log_backend
# Clippy broken with embedded tests
@@ -100,10 +103,7 @@
# cache invalidated when your host C++ config changes, causing many rebuilds
# of protoc (https://pwbug.dev/315871648).
common --experimental_exclude_defines_from_exec_config
-
-# This option breaks being able to select the nightly toolchian for the exec
-# config. See above for why it's enabled in Pigweed.
-# common --experimental_exclude_starlark_flags_from_exec_config
+common --experimental_exclude_starlark_flags_from_exec_config
# Enforces consistent action environment variables. This is important to
# address Protobuf's rebuild sensitivity on changes to the environment
