Pending "Checking pipeline status"

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

A new merge request contains gets Could not retrieve the pipeline status. For troubleshooting steps, read the documentation.

Steps to reproduce

1. gitlab-ci must have a complex conditional trigger for the pipeline(e.q. only/changes):

 only:
   changes:
     - dir1/dir2/*

2. Create a new merge request. Do changes on the new branch.
3. Make commit wich trigger pipeline execution(e.q. change file in dir1/dir2/ folder). The pipeline will be executed and passed.
4. Make another commit with changes in some dir3, not under dir1/dir2. The pipeline will be not be triggered.
5. Check to merge the request once again.

What is the current bug behavior?

Merge requests with "Could not retrieve the pipeline status. For troubleshooting steps, read the documentation."

What is the expected correct behavior?

During merge requests "checking pipeline status" should be skipped if there is no pipeline was executed after the last commit to the branch.

Results of GitLab environment info

System information
System:		Ubuntu 16.04
Current User:	git
Using RVM:	no
Ruby Version:	2.6.6p146
Gem Version:	2.7.10
Bundler Version:1.17.3
Rake Version:	12.3.3
Redis Version:	5.0.9
Git Version:	2.28.0
Sidekiq Version:5.2.9
Go Version:	go1.6.2 linux/amd64

GitLab information
Version:	13.3.6
Revision:	15c2c8c66db
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	11.7
URL:		https://mygitlab
HTTP Clone URL:	https://mygitlab/some-group/some-project.git
SSH Clone URL:	git@mygitlab:some-group/some-project.git
Using LDAP:	yes
Using Omniauth:	yes
Omniauth Providers: saml

GitLab Shell
Version:	13.6.0
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
GitLab Shell path:		/opt/gitlab/embedded/service/gitlab-shell
Git:		/opt/gitlab/embedded/bin/git 

Possible workaround

push a new empty commit with [ci skip]