Code coverage not presented while using gitlab runner 17.0.0/16.11.1
Summary
The coverage percentage number is not presented in UI after upgrading GitLab Runner from 16.10.0 to 16.11.1 or 17.0.0. Artifacts collected are the same but the coverage number in the job list or job view is empty.
The only difference is in the version of GitLab Runner and helper.
This was verified by downgrading to 16.10.0 where everything works as expected.
Note: FF_TIMESTAMPS
feature flag is enabled.
Relevant logs and/or screenshots
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
- Disable
FF_TIMESTAMPS
feature flag - Fix code that scans logs in the Rails app
Edited by Pedro Pombeiro