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

Explicitly enable workspace mode on Bazel CI #2250

Merged
merged 2 commits into from
Nov 14, 2024

Conversation

avdv
Copy link
Member

@avdv avdv commented Sep 24, 2024

(except for Bazel 6)

Fixes #2237

@avdv
Copy link
Member Author

avdv commented Sep 24, 2024

@sgowroji PTAL, does this look reasonable to you?

@avdv avdv requested a review from ylecornec November 6, 2024 13:32
@avdv avdv added the merge-queue merge on green CI label Nov 13, 2024
@mergify mergify bot merged commit 069fc77 into master Nov 14, 2024
119 checks passed
@mergify mergify bot deleted the cb/fix-bazel-head-workspace branch November 14, 2024 13:33
@mergify mergify bot removed the merge-queue merge on green CI label Nov 14, 2024
@avdv
Copy link
Member Author

avdv commented Nov 14, 2024

Seems this is no longer too relevant, as I just discovered that rules_haskell has been removed from the bazel@HEAD + downstream CI pipeline (see bazelbuild/continuous-integration@a423d66)

The reason was that it should be covered by the BCR compatibility test now, but AFAICS this only runs for the top 100 BCR modules...

See also https://github.com/bazelbuild/continuous-integration/tree/master/buildkite/bazel-central-registry#bcr-bazel-compatibility-test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bazel CI] FATAL: Bazel crashed due to an internal error while evaluating node
2 participants