-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
checkout@v2 unable to write pack file #316
Comments
Weird. Curious if others are hitting this too. One other workaround to consider is adding a script to steps:
- name: git gc
shell: bash
run: |
if [ -d '.git' ]; then
echo Running git gc
git gc
fi
- uses: actions/checkout@v2
fetch-depth: 0
lfs: 'true' |
@TingluoHuang thoughts? |
I've been getting this issue with |
اگر دوست داری در پروژه باشی و به نتایج مطلوب برسی به کارت با قدرت ادامه بده تا در آینده ای نزدیک پاداش خوبی بگیری و کاری برای مردم جهان انجام دادی من همه رو تحت نظر دارم خیالت راحت |
|
Im also seeing this as a problem: This only happened once I added the "fetchDepth" property. Worked for 2 years- checkout: self
clean: true Broke after 2 deployments- checkout: self
clean: true
fetchDepth: 1 The only difference Im seeing is from the git command that is produced which shouldn't matter but I will share just incase I don't see anything... With fetchDepth:git -c http.extraheader="AUTHORIZATION: bearer ***" fetch --force --tags --prune --progress --no-recurse-submodules --depth=1 origin +0fa816424dc963fa60b63a54e1d593eea28a834f:refs/remotes/origin/0fa816424dc963fa60b63a54e1d593eea28a834f Without fetchDepth:git -c http.extraheader="AUTHORIZATION: bearer ***" fetch --force --tags --prune --progress --no-recurse-submodules --unshallow origin |
Found the root cause (For me atleast). What was happening was someone renamed a branch and the pipeline was not set to cleanup its workspace before starting. This means, it was doing jobs:
- job: job_name
...
workspace:
clean: all # what to clean up before the job runs
...
Info can be found here on how this |
Occasionally, the
checkout@v2
step fails with the output below.Once the runner gets into this state, it will continue to fail until we remote into our self-hosted runner and execute
git gc
:Our configuration looks like:
Not sure if this is somehow related to
checkout@v2
automatically disabling garbage collection?https://github.com/actions/checkout/blob/main/src/git-source-provider.ts#L91
The text was updated successfully, but these errors were encountered: