-
Notifications
You must be signed in to change notification settings - Fork 98
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
Disallow using CROSSTOOL to select the cc_toolchain label #216
Comments
Reenable once bazelbuild/bazel-toolchains#216 is fixed and users are updated
Working on this. |
You're amazing Xin! Thank you! |
Ok. This is a little more complicated than I initially thought. The reason why it is failing is because the buildkite CI is using old toolchain configs (0.16.1), and those are not compatible with bazel head. So the fix would be I'll first update all bazel rule repos' WORKSPACE pin of bazel_toolchains to our latest, which will include our latest toolchain configs for Bazel 0.18.0. Then I'll update the toolchain flags in Buildkite CI. |
And by all rules you mean rules_go, rules_rust, rules_kotlin, and rules_scala, right? Because others were not failing? |
Yes. All the rules that enabled rbe_ubuntu1604 platform in their buildkite ci. |
I'm creating a PR in bazel-toolchains repo first to add a latest alias to crosstool and toolchain targets, so we don't need to modify buildkite configs in the future again (in most cases). |
Do not submit until all PRs to update @bazel_toolchains WORKSPACE pin are merged. bazelbuild/bazel-toolchains#216
Do not submit until all PRs to update @bazel_toolchains WORKSPACE pin are merged. bazelbuild/bazel-toolchains#216 bazelbuild#319
Do not submit until all PRs to update @bazel_toolchains WORKSPACE pin are merged. bazelbuild/bazel-toolchains#216 bazelbuild#319
Do not submit until all PRs to update @bazel_toolchains WORKSPACE pin are merged. bazelbuild/bazel-toolchains#216 #319
Can this be closed now? |
afaik yes, please reopen if there are any issues related to this still pending. |
Reenable once bazelbuild/bazel-toolchains#216 is fixed and users are updated
Do not submit until all PRs to update @bazel_toolchains WORKSPACE pin are merged. bazelbuild/bazel-toolchains#216 bazelbuild#319
- Prepare for BCR release as 0.10.0 - Rename repo name to toolchains_llvm - Upgrade Go version in tests and remove -nopie flag - Combine lint and tests workflow
Hello :)
I'm back again, I promise this is the last time. Today the incompatible flag for bazelbuild/bazel#6382 has been flipped, and it affects the bazel toolchains (https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/539#9c3cb2d3-791d-4e1f-944d-f768fb2810be). Please see migration docs here: https://docs.bazel.build/versions/master/skylark/backward-compatibility.html#disallow-using-crosstool-to-select-the-cc_toolchain-label, and let me know if you have problems.
Extra points for also updating bazel-toolchains versions in rules_go, rules_rust, rules_kotlin, and rules_scala, but I can also do that.
Please create an issue at https://github.com/bazelbuild/continuous-integration to reenable bazel-toolchains on the downstream pipeline.
The text was updated successfully, but these errors were encountered: