-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
rules_go & rules_python are failing in Downstream CI with Bazel@HEAD #18346
Labels
area-Bzlmod
Bzlmod-specific PRs, issues, and feature requests
breakage
P1
I'll work on this now. (Assignee required)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
Comments
/cc @SalmaSamy @Wyverald |
meteorcloudy
added
type: bug
P1
I'll work on this now. (Assignee required)
breakage
area-Bzlmod
Bzlmod-specific PRs, issues, and feature requests
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
labels
May 8, 2023
Should be reproducible with https://github.com/bazelbuild/rules_python/tree/main/examples/bzlmod_build_file_generation |
@bazel-io flag |
bazel-io
added
the
potential release blocker
Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone
label
May 16, 2023
@bazel-io fork 6.3.0 |
bazel-io
removed
the
potential release blocker
Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone
label
May 16, 2023
iancha1992
pushed a commit
to iancha1992/bazel
that referenced
this issue
May 18, 2023
Fixes bazelbuild#18346 At this point we are creating a rule from an extension repospec and that is always public PiperOrigin-RevId: 532558852 Change-Id: I245de0a23f92ba6283be4bf3be6af4863b7a8c68
iancha1992
added a commit
that referenced
this issue
May 19, 2023
…el@HEAD (#18447) * Store repospec instead of package for module extension PiperOrigin-RevId: 529679264 Change-Id: Ib9d410f5de1bac171c3c6f642b8584986181e44b * Stop checking .bzl files visibility in RepoRuleFunction Fixes #18346 At this point we are creating a rule from an extension repospec and that is always public PiperOrigin-RevId: 532558852 Change-Id: I245de0a23f92ba6283be4bf3be6af4863b7a8c68 --------- Co-authored-by: salma-samy <salmasamy@google.com>
fweikert
pushed a commit
to fweikert/bazel
that referenced
this issue
May 25, 2023
Fixes bazelbuild#18346 At this point we are creating a rule from an extension repospec and that is always public PiperOrigin-RevId: 532558852 Change-Id: I245de0a23f92ba6283be4bf3be6af4863b7a8c68
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-Bzlmod
Bzlmod-specific PRs, issues, and feature requests
breakage
P1
I'll work on this now. (Assignee required)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
rules_go: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3007#0187f91d-2018-4dd0-b272-79d934978ac3
rules_python : https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3007#0187f91d-2990-4989-9b6e-68aaf097469e
Logs:
Caused by a6ebf07 :
CC @meteorcloudy
The text was updated successfully, but these errors were encountered: