Skip to content

Conversation

@TimofteBogdan1900
Copy link

@TimofteBogdan1900 TimofteBogdan1900 commented Jan 27, 2026

Changes proposed

  • code coverage should run on each PR
  • on a PR , independent of tests passing/failing the Google Test logs are uploaded for debugging purposes
  • on release action the zipped code coverage is not a nested zip (minor change)

@TimofteBogdan1900 TimofteBogdan1900 changed the title Trigger a PR Run Code coverage for each opened PR Jan 27, 2026
@TimofteBogdan1900 TimofteBogdan1900 marked this pull request as ready for review January 27, 2026 16:47
@LittleHuba
Copy link
Contributor

Hey @TimofteBogdan1900, thanks for your contribution.
Currently the coverage toolchain does not give very reliable results. Therefore we did not activate it on PR runs yet, to not confuse people.
We will take a look at this PR as soon as we have capacity to dig into the coverage topic some more. This should happen next week hopefully.
Just wanted to let you know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants