Git error after some executions

[Maykonn]

The checkout action works fine (do the private repo checkout) until be executed I'm sure but something like 4 or 5 times. I mean, after some executions I'm getting the following output error of retries:

Run actions/checkout@v2
  with:
    repository: MyPrivate/Repo
    token: ***      # IT IS A GITHUB Personal Access Token
    ref: SRQ-644/SRQ-1099_php7_upgrade'
    path: test/test-path
    fetch-depth: 1
    persist-credentials: true
    clean: true
    lfs: false
Added matchers: 'checkout-git'. Problem matchers scan action output for known warning or error strings and report these inline.
Syncing repository: MyPrivate/Repo
Working directory is '/home/runner/work/TestActionRepo/TestActionRepo/test/test-path'
/usr/bin/git version
git version 2.24.1
/usr/bin/git init /home/runner/work/TestActionRepo/TestActionRepo/test/test-path
Initialized empty Git repository in /home/runner/work/TestActionRepo/TestActionRepo/test/test-path/.git/
/usr/bin/git remote add origin https://github.com/MyPrivate/Repo # IT IS HYPOTHETICAL PRIVATE REPO URL
/usr/bin/git config --local gc.auto 0
/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
/usr/bin/git config --local http.https://github.com/.extraheader AUTHORIZATION: basic ***
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/SRQ-644/SRQ-1099_php7_upgrade'*:refs/remotes/origin/SRQ-644/SRQ-1099_php7_upgrade'* +refs/tags/SRQ-644/SRQ-1099_php7_upgrade'*:refs/tags/SRQ-644/SRQ-1099_php7_upgrade'*
The process '/usr/bin/git' failed with exit code 1
Waiting 17 seconds before trying again
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/SRQ-644/SRQ-1099_php7_upgrade'*:refs/remotes/origin/SRQ-644/SRQ-1099_php7_upgrade'* +refs/tags/SRQ-644/SRQ-1099_php7_upgrade'*:refs/tags/SRQ-644/SRQ-1099_php7_upgrade'*
The process '/usr/bin/git' failed with exit code 1
Waiting 17 seconds before trying again
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/SRQ-644/SRQ-1099_php7_upgrade'*:refs/remotes/origin/SRQ-644/SRQ-1099_php7_upgrade'* +refs/tags/SRQ-644/SRQ-1099_php7_upgrade'*:refs/tags/SRQ-644/SRQ-1099_php7_upgrade'*
Removed matchers: 'checkout-git'
##[error]The process '/usr/bin/git' failed with exit code 1
##[error]Node run failed with exit code 1

As I said, this retries and then the output error happens randomly after some Action executions and then after I retry 2 or 3 times by clicking to re-run the action steps it eventually gets working again.

[ericsciple]

@Maykonn are you using a self-hosted runner or one of the hosted runners?

[Maykonn]

@ericsciple I'm using the Github hosted runner.

[ericsciple]

@Maykonn thanks. Sorry meant to reply sooner.

Does this happen occasionally or are you running into this daily? Service availability shows issue on Dec 13.

If a daily thing, i'm wondering whether it's a specific data center for the hosted runner. Do you see the issue on all runners (ubuntu-latest, macos-latest, windows-latest)? If so would point to git service instead of runner connectivity. If one of the runners, not the others, would point to hosted runner network availability.

[ericsciple]

@bryanmacfarlane @TingluoHuang does the runner track network health (ping etc)? Even if so, not sure where would surface. In this case hosted runners.

Sounds like an issue with either git service, or network of hosted runners. How do we route these issues? Is there generally useful docs or guidance for troubleshooting? Otherwise burden on every action that interacts with GitHub service, or even network.

[Maykonn]

@ericsciple thanks for your help. I ran the action two times again to test it right now, and on the first time the checkout worked without problems, but in a second test, I got the same error that I described days ago. Tested only with ubuntu-latest runner.

[ericsciple]

@hross fyi

[bryanmacfarlane]

@ericsciple for network health, you may want to follow up with compute. You might also want to check with dot com repo folks to see if the times line up with anything.

[Casperhr]

This happens to me when I merge into master

on:
pull_request:
paths:
- '.md'
- '.txt'

[Scrum]

@ericsciple Hi, I also got the same error, is there a solution for this?
https://github.com/vuejs/awesome-vue/runs/553645979?check_suite_focus=true

[ericsciple]

Can you try setting the following env vars so fetch will print more info:

GITHUB_TRACE=1
GIT_CURL_VERBOSE=1

For example:

jobs:
  foo:
    steps:
      - uses: actions/checkout@v2
        env:
          GIT_TRACE: 1
          GIT_CURL_VERBOSE: 1

[sid22]

Seeing the same issue, Using github runners, ubuntu-latest

[kane2266]

7497977Z ##[group]Run

[kane2266]

Jobs

[kane2266]

reply+AP6EPBFSZIMS4ALPEO3SFHV5B7V5LEVBNHHCCB53RA@reply.github.com