Exclude GCC implicit exception branches from coverage report - #170
Conversation
GCC's --coverage flag generates 2 branches for every function call (normal return vs exception thrown), causing gcov to report "1 of 2 conditions" on simple calls like writeObjects(). Adding gcovr's --exclude-throw-branches and --exclude-unreachable-branches filters these compiler-generated branches from the SonarCloud coverage report. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe GitHub Actions deploy workflow is updated to add two exclusion filters ( Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Comment |
|



Summary
--exclude-throw-branchesand--exclude-unreachable-branchesflags to the gcovr command in CI--coveragegenerates 2 branches for every function call (normal return vs exception thrown), causing SonarCloud to report "1 of 2 conditions" on simple calls likewriteObjects()that have no actual branching logicTest plan
🤖 Generated with Claude Code
Summary by CodeRabbit