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

The process '/usr/bin/git' failed with exit code 1 #1326

Open
agluszak opened this issue May 17, 2023 · 11 comments
Open

The process '/usr/bin/git' failed with exit code 1 #1326

agluszak opened this issue May 17, 2023 · 11 comments

Comments

@agluszak
Copy link

For some reason git started failing on checkout after I enabled auto-commiting changes made by prettier

Fetching the repository
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/update/jsoniter-scala-core-2.23.0*:refs/remotes/origin/update/jsoniter-scala-core-2.23.0* +refs/tags/update/jsoniter-scala-core-2.23.0*:refs/tags/update/jsoniter-scala-core-2.23.0*
  The process '/usr/bin/git' failed with exit code 1
  Waiting 20 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/update/jsoniter-scala-core-2.23.0*:refs/remotes/origin/update/jsoniter-scala-core-2.23.0* +refs/tags/update/jsoniter-scala-core-2.23.0*:refs/tags/update/jsoniter-scala-core-2.23.0*
  The process '/usr/bin/git' failed with exit code 1
  Waiting 15 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/update/jsoniter-scala-core-2.23.0*:refs/remotes/origin/update/jsoniter-scala-core-2.23.0* +refs/tags/update/jsoniter-scala-core-2.23.0*:refs/tags/update/jsoniter-scala-core-2.23.0*

See: https://github.com/build-server-protocol/build-server-protocol/actions/runs/5003971723/jobs/8966282180#step:2:129

@qxmips
Copy link

qxmips commented Jun 7, 2023

I have same issue.

@cwg50805
Copy link

Same :(

@guychienll
Copy link

I have same issue too !

@ArjunDandagi
Copy link

BUMP:
we are seeing the same issue in our actions runner now

@polytopes-design
Copy link

Same

@haooliveira84
Copy link

same here :(

@kenorb
Copy link

kenorb commented Apr 20, 2024

Fetching the repository
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/v2.000-dev*:refs/remotes/origin/v2.000-dev* +refs/tags/v2.000-dev*:refs/tags/v2.000-dev*
  The process '/usr/bin/git' failed with exit code 1
  Waiting 20 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/v2.000-dev*:refs/remotes/origin/v2.000-dev* +refs/tags/v2.000-dev*:refs/tags/v2.000-dev*
  The process '/usr/bin/git' failed with exit code 1
  Waiting 14 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/v2.000-dev*:refs/remotes/origin/v2.000-dev* +refs/tags/v2.000-dev*:refs/tags/v2.000-dev*
  ##[debug]Unsetting HOME override
  ::remove-matcher owner=checkout-git::
  ##[debug]Removed matchers: 'checkout-git'
  Error: The process '/usr/bin/git' failed with exit code 1
  ##[debug]Node Action run completed with exit code 1

The same error after dozens of re-runs.

Usage:

      - uses: actions/checkout@v4
        with:
          path: Include/EA31337-strategies
          ref: v2.000-dev
          repository: EA31337/EA31337-strategies
          submodules: recursive

I've tested actions/checkout@v3, didn't work either (same error).

It's possible that I'm cloning git repository on top of another cloned repository and there is some kind of confusion?


Update: I've refactored my actions by moving checkout of each repo into separate jobs then upload source code files as artifact, then download it from another one. This workaround worked for me.

kenorb added a commit to EA31337/EA31337-strategies that referenced this issue Apr 20, 2024
kenorb added a commit to EA31337/EA31337-strategies that referenced this issue Apr 20, 2024
@hieutomra
Copy link

Same error and symptom for us.
We are running with self-hosted runner. I tried to run the same command as the runner would and with export GIT_TRACE=1

[...]
09:45:10.394902 run-command.c:654       trace: run_command: GIT_DIR=.git git remote-https origin https://github.com/REDACTED
09:45:10.395717 git.c:745               trace: exec: git-remote-https origin https://github.com/REDACTED
09:45:10.395736 run-command.c:654       trace: run_command: git-remote-https origin https://github.com/REDACTED
Username for 'https://github.com': foo
Password for 'https://foo@github.com': 
09:45:22.693484 run-command.c:654       trace: run_command: git maintenance run --auto --no-quiet
09:45:22.694565 git.c:458               trace: built-in: git maintenance run --auto --no-quiet

$ echo $? 
1 

@ElRojo
Copy link

ElRojo commented Apr 23, 2024

~I'm also having this issue. The ref is a tag and it works on some tags, but not on others. ~

edit: branch didn't exist in my case.

@asombaty
Copy link

I am having this issue for the past week now.

@Olfi01
Copy link

Olfi01 commented May 29, 2024

I had the same problem and fixed it. In my case, the branch was still called master, but I was trying to checkout main.

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