Flag --incompatible_disable_starlark_host_transitions will break Bazel in 7.0
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:
- CentOS OpenJDK 11
- MacOS OpenJDK 11
- MacOS OpenJDK 8
- Ubuntu 18.04 OpenJDK 11
- Ubuntu 18.04 OpenJDK 11
- Ubuntu 20.04 OpenJDK 11
- Windows OpenJDK 11
- Ubuntu 18.04 OpenJDK 11
- CentOS OpenJDK 11
- MacOS OpenJDK 11
- Ubuntu 18.04 OpenJDK 11
- Ubuntu 20.04 OpenJDK 11
- Windows OpenJDK 11
- Ubuntu 18.04 OpenJDK 11
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.
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 https://github.com/bazelbuild/bazel/issues/17032.
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.
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!