Coverage check approval rule requires approval, even though code coverage increased.

Summary

Although the code coverage of my new version of the code increased (+4% as reported in the UI), a merge request approval is required.

As defined in the UI and the documentation, this shall not be the case.

Steps to reproduce

Example Project

What is the current bug behavior?

According to the job results, code coverage increased by 4% in the latest pipeline run. Nevertheless, the merge request cannot be merged because an approval is required related to the Coverage-Check approval rule.

What is the expected correct behavior?

When a code coverage job does not detect a decline of the code coverage, then the rule should not be triggered.

Relevant logs and/or screenshots

image__2_

Output of checks

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