-
Notifications
You must be signed in to change notification settings - Fork 15
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
Investigate go-git concurrency issues #162
Comments
Another option would be to bail on go-git and use a wrapper for the real git. https://github.com/ldez/go-git-cmd-wrapper?tab=readme-ov-file |
@mingxzhao reported a back to back error in this job instructlab/taxonomy#80 :
|
This was referenced Apr 18, 2024
nerdalert
added
good first issue
Good for newcomers
and removed
good first issue
Good for newcomers
labels
Apr 29, 2024
Here was another incident of this: instructlab/taxonomy#1060 |
nerdalert
added a commit
to nerdalert/instructlab-bot
that referenced
this issue
May 23, 2024
- delete the repo after the job completes - clone at the beginning of a job - resolves the retries that were present in all of the job runs Closes instructlab#162 Signed-off-by: Brent Salisbury <bsalisbu@redhat.com>
nerdalert
added a commit
to nerdalert/instructlab-bot
that referenced
this issue
May 23, 2024
- delete the repo after the job completes - clone at the beginning of a job - resolves the retries that were present in all of the job runs Closes instructlab#162 Signed-off-by: Brent Salisbury <bsalisbu@redhat.com>
nerdalert
added a commit
to nerdalert/instructlab-bot
that referenced
this issue
May 23, 2024
- delete the repo after the job completes - clone at the beginning of a job - resolves the retries that were present in all of the job runs e.g. "Retrying fetching updates, attempt 1/5 2/5 3/5..." Closes instructlab#162 Signed-off-by: Brent Salisbury <bsalisbu@redhat.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consistently seeing 3/3 on retries. Either bump them up or dig into the issue. Not a big deal to just add more retries imo since it's just a local thing but worth a little time investigating.
Example:
The text was updated successfully, but these errors were encountered: