-
Notifications
You must be signed in to change notification settings - Fork 81
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
Bazel CI: rules_haskell failing with Bazel@HEAD in downstream #1657
Comments
/cc @aherrmann |
@meteorcloudy Thank you for notifying! I can reproduce this locally:
I think this has to do with the Asterius toolchain depending on the NodeJS toolchain and the change of the default of
and Bazel 4 to fail with
@ylecornec could you take a look at this? A good fix may be to obtain the NodeJS toolchain not via a direct toolchain dependency but through a tool dependency with |
rules_haskell is now green with Bazel@HEAD: https://buildkite.com/bazel/bazel-at-head-plus-disabled/builds/1142#8012be70-45bd-4ffb-8628-d249462fff44 I'll re-enable it in downstreaml |
rules_haskell has been fixed in: tweag/rules_haskell#1650 tweag/rules_haskell#1657
rules_haskell has been fixed in: tweag/rules_haskell#1650 tweag/rules_haskell#1657
rules_haskell has been fixed in: tweag/rules_haskell#1650 tweag/rules_haskell#1657
After the fixes of #1653 and #1655, there are new failures with Bazel@HEAD
https://buildkite.com/bazel/bazel-at-head-plus-disabled/builds/1135#bd2706c7-71d5-4ff3-ba18-0db702a7456a
This is reproducible with Bazel 5.0.0rc2:
The text was updated successfully, but these errors were encountered: