Code coverage statistics not updating after 18th of March
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
A customer is reporting that the code coverage statistics have not been updating since the 18th of March, even though the graph is supposed to display all history test data. I can see builds running code coverage since, though.
Even though the .gitlab-ci.yml file seems to contain a valid coverage section, including a valid regex, the code coverage statistics have not been updating for more than two months.
What is the current bug behavior?
See summary. Code coverage statistics have not been updating for two months even though the configuration looks valid, and coverage jobs have run since.
What is the expected correct behavior?
Code coverage statistics should update daily if coverage jobs are running every day.
Relevant logs and/or screenshots
Screenshot is attached to ZD ticket (see ticket in comments).
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)