-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Make env on test rules override --test_env #22420
Make env on test rules override --test_env #22420
Conversation
0ddb8e6
to
2b4265c
Compare
src/main/java/com/google/devtools/build/lib/exec/TestPolicy.java
Outdated
Show resolved
Hide resolved
2b4265c
to
6c23b63
Compare
hey @lberki, do you perhaps know if this ordering/overwriting was intentional or accidental? With this PR, there might be a risk that a Starlark rule overwrites PATH variable or some other important variables. (or it might be a feature). Or I might be overthinking it. |
Doing some code archaeology (I went back as far as cl/146237448), it looks like this ordering was what Blaze did before it was Bazel and no one wanted to change the semantics for fear of breaking some legacy behavior. |
Ok. So let's see if that's still there. |
@bazel-io flag |
@bazel-io fork 7.2.0 |
Fixes bazelbuild#14418 Closes bazelbuild#22420. PiperOrigin-RevId: 635740423 Change-Id: Iffd4d172c4175be2e1b6cfad04ddad2759adb987
Fixes #14418