-
Notifications
You must be signed in to change notification settings - Fork 74
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
pull-test.sh: fix "git subtree pull" errors #264
Conversation
Without allowing to fetch missing file content, "git subtree pull" fails: remote: warning: lazy fetching disabled; some objects may not be available remote: fatal: could not fetch b18c53581356c52a220a2baf1c8cf3fd9c57dda6 from promisor remote error: git upload-pack: git-pack-objects died with error. fatal: git upload-pack: aborting due to possible repository corruption on the remote side. remote: aborting due to possible repository corruption on the remote side.� fatal: protocol error: bad pack header
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I don't know yet whether this is sufficient... let's see. |
/release-note-none |
/assign @huww98 |
@pohly: GitHub didn't allow me to assign the following users: huww98. Note that only kubernetes-csi members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/assign @jsafrane |
@pohly: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/lgtm |
It needs also a new go + re-vendoring. I think we can add those to #261 |
The go.mod that needs update is located at csi-test repo. So I think it cannot be fixed by PR in this repo. |
I agree that the failure in pull-kubernetes-csi-release-tools-csi-test can be ignored. That job is intentionally declared as "not required". The vendoring issue needs to be sorted out when updating csi-release-tools in the csi-test repo. I don't know what Trivy is complaining about. It seems to block merging? |
Without allowing to fetch missing file content, "git subtree pull" fails: