Merge button red, pipeline widget stuck on "Checking pipeline status", yet the last pipeline is green
NOTE: This issue is currently is being marked as closed because we've delivered on improved mergeability checks making it easier to diagnose and remedy this type of issue if it occurs again.
Summary
On this MR !36496 (merged), I had a red Merge button while the Pipelines tab showed the last status as green. However, the MR widget to display pipeline status was stuck on "Checking pipeline status".
This may be a bug, which should be identified first, but can likely be addressed by UX in any case. I am creating a separate issue for documentation improvement.
Steps to reproduce
I am not exactly sure of what caused this, but the steps can be retraced by reviewing the MR history. When re-running the latest pipeline jobs, the button did not change, even though the jobs were green. After rebasing onto master and pushing (because the branch was 1000+ commits behind), the new pipeline immediately resulted in the button changing to "Merge When Pipeline Succeeds" and then to a green "Merge" button when it passed. Could it in part be that re-running the jobs of the previous pipeline was insufficient but starting a new pipeline would have worked?
Example Project
N/A
What is the current bug behavior?
The Merge button can be red without an indication as to why, even while the last pipeline is green. Insufficient indication of the state and what to do via the UI.
What is the expected correct behavior?
The button would either be green, or be red with an explanation. "Checking pipeline status" would not persist.
Relevant logs and/or screenshots
I believe I found the second-from-the-top pipeline green today, but it had been some days so I re-ran the jobs to be sure. The merge button was red after doing so (while the pipeline widget showed the above status), but I'm not sure how long it was red before that or how long the pipeline widget hadn't been working.
The top pipeline was created by pushing after rebasing, which is the pipeline that resulted in a green merge button.
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.