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

Calling retry checkout cause checkout::refbased: command not found #437

Open
ThomasKwan-shopline opened this issue Nov 8, 2023 · 3 comments

Comments

@ThomasKwan-shopline
Copy link

As mention in title, when I calling retry checkout in my task, the log shows following error. So how can I solve this issue?

environment: line 11: checkout::refbased: command not found00:00
environment: line 17: checkout::metric: command not found00:00
[1/3] Execution Failed with exit status 127. Retrying.00:00
environment: line 11: checkout::refbased: command not found00:00
environment: line 17: checkout::metric: command not found00:00
[2/3] Execution Failed with exit status 127. Retrying.00:00
environment: line 11: checkout::refbased: command not found00:00
environment: line 17: checkout::metric: command not found00:00
[3/3] Execution Failed with exit status 127. No more retries.

my prologue

commands:
  - sem-version go 1.15
  - mkdir -vp "${SEMAPHORE_GIT_DIR}" "$(go env GOPATH)/bin"
  - retry checkout
@radwo
Copy link
Member

radwo commented Nov 8, 2023

Hi Thomas,

I understand you're encountering issues with the checkout task. To clarify, the checkout method is designed with an internal retry mechanism to handle transient errors automatically. This means there's no need for an additional external retry.

For your reference and to see how the retry logic is implemented, you can check the source code at the following link: https://github.com/semaphoreci/toolbox/blob/master/libcheckout. This should give you a clear understanding of the retry process.

If there's anything else we can help you with, please don't hesitate to let us know.

@ThomasKwan-shopline
Copy link
Author

I see, btw have remove the retry and run the checkout directly, however I have face the same issue like this issue (link: #386). So how can I solve it?

@radwo
Copy link
Member

radwo commented Nov 8, 2023

Thank you for the update. It would be best to take a closer look at the specifics of your job to provide a tailored solution.

Please get in touch with our support team with the Job ID and link to this issue.

You can contact support by emailing [email protected] or via the support section on our website.

Please provide as much detail as possible so they can assist you efficiently.

We're here to help you get this resolved as quickly as possible.

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

No branches or pull requests

2 participants