Skip to content
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

Flag --incompatible_disable_starlark_host_transitions will break Bazel in 7.0 #17043

Closed
keertk opened this issue Dec 16, 2022 · 4 comments
Closed
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Starlark-Interpreter Issues involving the Starlark interpreter used by Bazel type: bug

Comments

@keertk
Copy link
Member

keertk commented Dec 16, 2022

Incompatible flag --incompatible_disable_starlark_host_transitions will be enabled by default in Bazel 7.0. Please migrate and unblock the flip of this flag.

The flag is documented here: bazelbuild/bazel#17032.

Please check the following CI builds for build and test results:

image

@brandjon
Copy link
Member

Looks like an issue for stardoc, but apparently the downstream CI build of Bazel itself somehow depends on stardoc?

Guess we'll have to address bazelbuild/stardoc#145, cut a stardoc release, and update whatever is pulling it into this build to the new version. Sasha will be back in January so may as well wait until then, since we have some time before 7.0.

@brandjon brandjon added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed untriaged labels Dec 19, 2022
@gregestren
Copy link
Contributor

Note that https://bazel-review.googlesource.com/c/bazel/+/208644 enables this flag by default, which I believe we can re-ping when we've closed this and #17032.

Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 23, 2024
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please post @bazelbuild/triage in a comment here and we'll take a look. Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Starlark-Interpreter Issues involving the Starlark interpreter used by Bazel type: bug
Projects
None yet
Development

No branches or pull requests

4 participants