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

hook git clone failures #15225

Closed
BenTheElder opened this issue Nov 11, 2019 · 5 comments
Closed

hook git clone failures #15225

BenTheElder opened this issue Nov 11, 2019 · 5 comments
Labels
area/prow/hook Issues or PRs related to prow's hook component kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@BenTheElder
Copy link
Member

What happened:

jsonPayload: {
  client: "git"   
  component: "hook"   
  file: "prow/git/git.go:389"   
  func: "k8s.io/test-infra/prow/git.retryCmd"   
  level: "warning"   
  msg: "Running /usr/bin/git [clone --mirror https://k8s-ci-robot:CENSORED@github.com/kubernetes/kubernetes /tmp/git880570593/kubernetes/kubernetes.git] returned error exit status 128 with output Cloning into bare repository '/tmp/git880570593/kubernetes/kubernetes.git'...
fatal: remote error: upload-pack: not our ref 6435c6df2a382b4e8278af486fb646e84089af80
fatal: The remote end hung up unexpectedly
."   
 }

What you expected to happen: cloning to work

How to reproduce it (as minimally and precisely as possible): unclear. this is happening in the prow.k8s.io deployment

Please provide links to example occurrences, if any: visible in the cluster logs if you have access

Anything else we need to know?: this is happening repeatedly.

@BenTheElder BenTheElder added kind/bug Categorizes issue or PR as related to a bug. area/prow/hook Issues or PRs related to prow's hook component labels Nov 11, 2019
@BenTheElder
Copy link
Member Author

looks like these are probably for unmerged commits. possibly just pushed

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 10, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/prow/hook Issues or PRs related to prow's hook component kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants