Failure type for retry

GitLab CI/CD
#1

I have a job that inherits from another job that just contains:

.global-retry:
  retry:
    max: 2
    when:
      - runner_system_failure
      - stuck_or_timeout_failure

This job is failing at the git level with:

Running with gitlab-runner 12.3.0 (a8a019e0)
  on pinwheel-racket BoyE4M-w
Using Docker executor with image pmatos/racket-ci:testdeps ...
Pulling docker image pmatos/racket-ci:testdeps ...
Using docker image sha256:6d32123379860f0b213f998aa49e7edabeb80f43b89b2ed3cbf16f83db4f75fe for pmatos/racket-ci:testdeps ...
Running on runner-BoyE4M-w-project-8928499-concurrent-5 via pinwheel...
Fetching changes with git depth set to 10...
Initialized empty Git repository in /builds/LinkiTools/racket/.git/
Created fresh repository.
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
Uploading artifacts...
WARNING: test.log: no matching files               
ERROR: No files to upload                          
ERROR: Job failed: exit code 1

It is, as you can see, not retrying. Which failure type fits these failure types so I can add it to my retry when list?

#2

Unfortunately I believe that this is a script_failure and that’s possibly why. We are seeing the same failure (the curl 18 transfer closed error) and I was looking to see if retry: would work for it but I’m not sure that it will.

I didn’t want to add script_failure since that’s indistinguishable from the job failing because of the actual script itself.

#3

Unfortunately I agree you might be correct but it’s not satisfactory because it is not a script_failure. It’s not in user script so it shouldn’t be a script failure.

#4