Exit Code 139 on CI / Runner Starting with 10.4.x

Please read this!

Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label.

For the Community Edition issue tracker:

For the Enterprise Edition issue tracker:

and verify the issue you're about to submit isn't a duplicate.

Please remove this notice if you're confident your issue isn't a duplicate.

Summary

CI Pipelines Failing with Exit Code 139

Steps to reproduce

  1. Commit code to repo
  2. Runner picks up job
  3. Runner checks out code checksum
  4. Job fails w/ exit code 139

Example Project

N/A

What is the current bug behavior?

Exit Code 139

What is the expected correct behavior?

Deployment successful.

Relevant logs and/or screenshots

Job log:

HEAD is now at fe84028 
Checking out fe840286 as master...
Skipping Git submodules setup
ERROR: Job failed: exit code 139```

### Output of checks
N/A

#### Results of GitLab environment info

System information System: RedHatEnterpriseWorkstation 7.4 Proxy: no Current User: git Using RVM: no Ruby Version: 2.3.6p384 Gem Version: 2.6.13 Bundler Version:1.13.7 Rake Version: 12.3.0 Redis Version: 3.2.11 Git Version: 2.14.3 Sidekiq Version:5.0.5 Go Version: unknown

GitLab information Version: 10.4.2-ee Revision: 30275e24 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.5 URL: https:// HTTP Clone URL: https:///some-group/some-project.git SSH Clone URL: git@:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: yes Using Omniauth: no

GitLab Shell Version: 5.11.0 Repository storage paths:

  • default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
#### Results of GitLab application Check

Checking GitLab Shell ...

GitLab Shell version >= 5.11.0 ? ... OK (5.11.0) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 2/1 ... ok 3/3 ... repository is empty 21/5 ... ok 19/8 ... ok 12/9 ... ok 12/11 ... ok 10/12 ... ok 12/13 ... ok 26/14 ... ok 16/17 ... ok 12/18 ... ok 11/19 ... repository is empty 12/20 ... ok 3/22 ... repository is empty 20/23 ... ok 23/27 ... ok 23/28 ... ok 23/29 ... repository is empty 20/30 ... repository is empty 16/31 ... ok 21/33 ... repository is empty 26/34 ... ok 27/35 ... ok 12/36 ... ok 12/38 ... ok 19/40 ... ok 12/41 ... ok 3/42 ... repository is empty 19/43 ... repository is empty 12/47 ... ok 16/48 ... ok 15/51 ... ok 19/52 ... repository is empty 14/54 ... ok 35/56 ... ok 35/60 ... ok 41/62 ... ok 4/64 ... ok 14/65 ... ok 66/69 ... ok 66/71 ... ok 14/73 ... ok 66/79 ... ok 66/80 ... ok 32/81 ... ok 66/82 ... ok 68/83 ... repository is empty 67/87 ... ok 67/88 ... ok 67/90 ... ok 67/91 ... ok 67/92 ... ok 67/93 ... ok 67/94 ... ok 67/95 ... ok 67/96 ... ok 67/97 ... ok 67/98 ... ok 67/99 ... ok 67/100 ... ok 67/101 ... repository is empty 66/102 ... ok 66/104 ... ok 66/106 ... repository is empty 3/107 ... ok 66/108 ... ok 66/109 ... ok 66/110 ... ok 3/111 ... repository is empty 66/112 ... ok 66/113 ... ok 66/114 ... ok 66/115 ... ok 66/116 ... ok 66/117 ... repository is empty 66/118 ... ok 66/119 ... ok 66/120 ... ok 66/121 ... ok 66/122 ... ok 66/123 ... ok 66/124 ... ok 66/125 ... ok 66/126 ... ok 66/127 ... ok 66/128 ... ok 21/130 ... ok 71/131 ... ok 67/132 ... ok 12/133 ... repository is empty 21/135 ... repository is empty 82/136 ... repository is empty 84/138 ... ok 13/143 ... ok 13/144 ... ok 71/149 ... ok 71/150 ... ok 26/157 ... ok 26/158 ... repository is empty 26/159 ... repository is empty 26/160 ... repository is empty 21/161 ... ok 93/163 ... repository is empty 94/166 ... ok 94/167 ... ok 94/168 ... ok

### Possible fixes
This error will sometimes go away by "Retry" on either the job or the pipeline. Issue is occurring now about 90% of submissions.
Edited by Les Dodson