Merge requests stuck in "Checking ability to merge automatically"

Summary

On all of the merge requests I handled today for the www-gitlab-com repo, the "Checking ability to merge automatically" icon appeared, but never disappeared. In most instances, after a few minutes, and after refreshing the page, it finally went away. I'm not certain, but it appeared to only go away after the build and pipelines had been completed (and then the page manually refreshed).

Steps to reproduce

Create a merge request. Observe.

Expected behavior

The "Checking ability to merge automatically" should (i) finish rapidly, and (not sure if this is expected, but it is certainly desirable) (ii) should be possible to stop .

Actual behavior

See description above.

Relevant logs and/or screenshots

Since the merge requests eventually did go through, I do not have useful links or outputs to share here.

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)

Output of checks

This bug happens on GitLab.com

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of 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)

Results of 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)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)