-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Per-target exec_properties overwrites (not merges with) --remote_default_exec_properties #10252
Comments
This recently bit us as well. |
As described in the doc:
So the current behaviour is correct but I am not sure whether it's expected. |
I read that as referring to the platform's In other words, if a platform doesn't have However, regardless of the platform's content, I expect the per-target Docs (in Common Definitions):
|
Same, I read " if an execution platform does not already set exec_properties." to mean the |
SGTM. I will make the fix into 5.0. |
…_properties (#14212) Per-target `exec_properties` was introduced by 0dc53a2 but it didn't take into account of `--remote_default_exec_properties` which provides default exec properties for the execution platform if it doesn't already set with `exec_properties`. So the per-target `exec_properties` overrides `--remote_default_exec_properties` instead of merging with them which is wrong. Fixes #10252. Closes #14193. PiperOrigin-RevId: 406337649 (cherry picked from commit 3a5b360) Co-authored-by: Chi Wang <[email protected]>
Description of the problem / feature request:
exec_properties
is a universal target attribute documented as:This doesn't seem to be working as expected when combined with
--remote_default_exec_properties
. Instead of merging, the default exec properties get completely ignored.The build is not using a
platform()
rule (thecontainer-image
name is too dynamic to easily put in a source file), so I would have expected--remote_default_exec_properties
to be used.What operating system are you running Bazel on?
Linux
What's the output of
bazel info release
?release 1.0.0
The text was updated successfully, but these errors were encountered: