Reputation: 31
I have a project with a gitlab CI for my school project for around 3 months now and never had an issue. But, yesterday morning when I wanted to commit my new code changes and push it to my Gitlab. This worked completely fine, however my CI keeps failing:
In text:
1 Running with gitlab-runner 13.9.0 (2ebc4dc4)
2 on
3 Preparing the "shell" executor
4 Using Shell executor...
6 Preparing environment
7 Running on
9 Getting source from Git repository
10 Fetching changes with git depth set to 50...
11 Reinitialized existing Git repository in
12 Checking out 437a9a83 as master...
13 error: bad signature 0x00000000
14 fatal: index file corrupt
16 Cleaning up file based variables
18 ERROR: Job failed: exit status 1
didn't notice my branch failed so I also merged this with
I was working in a separate branch and didn't notice my branch failed, so I also merged this with my main branch so main
isn't working as well.
Upvotes: 1
Views: 395
Reputation: 1323793
This is mentioned in gitlab-org/gitlab-runner
issue 3290
The Git index file got corrupted causing the build to fail and the runner is not able to recover.
It should be able to handle this by deleting the index file and resetting the repo
As in "How to resolve “Error: bad index – Fatal: index file corrupt” when using Git"
See if the issue persists in a second GitLab pipeline, created for testing, in order to force a new clone of the same repository.
Upvotes: 1