-
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
Bazel's git_repository and new_git_repository is not compatible with the latest Git version #17040
Labels
P1
I'll work on this now. (Assignee required)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
Comments
meteorcloudy
added
type: bug
P1
I'll work on this now. (Assignee required)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
labels
Dec 16, 2022
copybara-service bot
pushed a commit
that referenced
this issue
Dec 16, 2022
Due to #17040 PiperOrigin-RevId: 495854505 Change-Id: I90d8d537e87f7ea51fa79b2847997c280baccf7f
copybara-service bot
pushed a commit
that referenced
this issue
Dec 16, 2022
…_test Due to #17040 PiperOrigin-RevId: 495878182 Change-Id: I69107cfd1bbc2468e62ac9804ca4a18fda87fa1b
5 tasks
@bazel-io fork 6.1.0 |
meteorcloudy
added a commit
that referenced
this issue
Jan 19, 2023
…_repository (#17247) - Added necessary flags to allow clone submodule from local repository. - We only have the starlark version of git repository rule and most test cases in two integration tests are duplicated. Fixes #17040 RELNOTES: None PiperOrigin-RevId: 498989149 Change-Id: I1eec3efa17382ddd0a608c0984e2f6c9f29c5c7c Co-authored-by: Googler <[email protected]>
hvadehra
pushed a commit
that referenced
this issue
Feb 14, 2023
Due to #17040 PiperOrigin-RevId: 495854505 Change-Id: I90d8d537e87f7ea51fa79b2847997c280baccf7f
hvadehra
pushed a commit
that referenced
this issue
Feb 14, 2023
…_test Due to #17040 PiperOrigin-RevId: 495878182 Change-Id: I69107cfd1bbc2468e62ac9804ca4a18fda87fa1b
hvadehra
pushed a commit
that referenced
this issue
Feb 14, 2023
…_repository - Added necessary flags to allow clone submodule from local repository. - We only have the starlark version of git repository rule and most test cases in two integration tests are duplicated. Fixes #17040 RELNOTES: None PiperOrigin-RevId: 498989149 Change-Id: I1eec3efa17382ddd0a608c0984e2f6c9f29c5c7c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P1
I'll work on this now. (Assignee required)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
The git version on Bazel CI's Windows VMs has just been upgraded, and some integration tests for git_repository/new_git_repository is failing:
https://storage.googleapis.com/bazel-untrusted-buildkite-artifacts/01851af9-6e76-4a64-9f5f-4abd2a74d22d/src%5Ctest%5Cshell%5Cbazel%5Cgit_repository_test%5Ctest_attempts%5Cattempt_1.log
Root cause is this Git update: https://lore.kernel.org/lkml/[email protected]/, but we need to somehow fix those integration tests and git_repository/new_git_repository rules.
The text was updated successfully, but these errors were encountered: