-
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
incompatible_disable_starlark_host_transitions #17032
Comments
Early evidence is this breaks Bazel's own tests: |
Testing this flag at https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/1365#_ |
Become compatible with `--incompatible_disable_starlark_host_transitions`, which will be flipped in Bazel 7. bazelbuild/bazel#17032
This will be required for bazel 7.0 due to bazelbuild/bazel#17032.
Become compatible with `--incompatible_disable_starlark_host_transitions`, which will be flipped in Bazel 7. bazelbuild/bazel#17032
Become compatible with `--incompatible_disable_starlark_host_transitions`, which will be flipped in Bazel 7. bazelbuild/bazel#17032
As of Bazel 6.2, this flag remains almost entirely unusable as the included version of rules_license still specifies |
/cc @aiuto |
Not near desk right now, but it sounds like we've got to upgrade a basal
62X release to a fresher rooms license. I'll take a look at that later this
week.
…On Mon, May 15, 2023, 12:11 PM Yun Peng ***@***.***> wrote:
/cc @aiuto <https://github.com/aiuto>
—
Reply to this email directly, view it on GitHub
<#17032 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXHHHEG3XU42SLKXB6OJR3XGJIU5ANCNFSM6AAAAAAS7BEDJE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yeech. Bazel at head and 6.x is using rules_license 0.0.3. I'll have 0.0.5 out later this week. We can upgrade both to that. |
Become compatible with `--incompatible_disable_starlark_host_transitions`, which will be flipped in Bazel 7. bazelbuild/bazel#17032
For bazelbuild/bazel#17032 (eliminate dependencies on `cfg = "host"`)
Preserves future Bazel compatibility: bazelbuild/bazel#17032 Extension of grpc#32021 which missed review.
Preserves future Bazel compatibility:bazelbuild/bazel#17032 Extension of #32021 which missed review. release notes: no Closes #35258 COPYBARA_INTEGRATE_REVIEW=#35258 from gregestren:master 7379674 PiperOrigin-RevId: 591092923
This is a no-op cleanup, 'host' is being renamed to 'exec', see: bazelbuild/bazel#17032
Change:
--incompatible_disable_starlark_host_transitions makes this Starlark syntax illegal:
Instead use:
Rationale:
Rules can't be configured for the host configuration, which is the machine Bazel rules on. They must be configured for the exec configuration, which is the machine that runs builds actions. Sometimes these are the same (local builds), but not always (remote execution builds).
exec
correctly captures these differences.Even with this flag disabled,
cfg = "host"
is an alias forcfg = "exec"
. So this is a no-op beyond the syntax cleanup.Expected error for unmigrated code:
The text was updated successfully, but these errors were encountered: