Pipeline/Job fails without output after artifacts expire

Summary

When a pipeline defines multiple stages and one of the earlier jobs creates an artifact with expiration, the first job after the artifact expiring fails after 0 seconds without any output.

Maybe failing is intended, but there should be at least an info why the pipeline fails.

Steps to reproduce

Create a pipeline with three stages, one job each. First stage defines a artifact with expiration 1 minute. Second job runs a sleep 2 minutes. Third job does an echo.

When running the pipeline, the third job will fail without any output.

Example Project

https://gitlab.com/fokoenecke/pipeline-fails-on-artifact-expire The project works on gitlab.com, but does not on our custom installation:

GitLab Community Edition 10.3.3
gitlab-runner 10.3.0

What is the current bug behavior?

My job fails without output.

What is the expected correct behavior?

Job should either run with a warning that an artifact has expired or fail with an error message.

Relevant logs and/or screenshots

job-artifact-fail

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:		
Current User:	git
Using RVM:	no
Ruby Version:	2.3.5p376
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.4
Go Version:	unknown

GitLab information
Version:	10.3.3
Revision:	888cf31
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
Using LDAP:	yes
Using Omniauth:	no


GitLab Shell
Version:	5.10.2
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

Expand for output related to the GitLab application check 
looks good