exclude bindings definition from coverage report, it's glue code, not application logic

Author: frs69wq

.github/workflows/build.yml

@@ -119,8 +119,8 @@ jobs:
         run: |
           cd build
           lcov --keep-going --ignore-errors mismatch --directory . --capture --output-file coverage.info
-          lcov --ignore-errors mismatch --remove coverage.info '*/test/*' -o coverage.info
-          gcovr --root .. -e '../test' -e '../examples' --sonarqube -o coverage.xml --exclude-throw-branches \
+          lcov --ignore-errors mismatch --remove coverage.info '*/test/*' '*/bindings/*' -o coverage.info
+          gcovr --root .. -e '../test' -e '../examples' -e '../src/bindings' --sonarqube -o coverage.xml --exclude-throw-branches \
                 --gcov-ignore-parse-errors --exclude-unreachable-branches
           # Strip branch attributes so SonarQube uses line coverage only
           # (gcovr's sonarqube format includes branch data that penalizes macro-generated conditionals like XBT_DEBUG)

sonar-project.properties

@@ -10,7 +10,7 @@ sonar.links.scm=https://github.com/simgrid/DTLMod/
 # Comma-separated paths to directories with sources (required)
 sonar.sources=src,include
 sonar.tests=test
-sonar.coverage.exclusions=test/** # do not consider test directory for coverage
+sonar.coverage.exclusions=test/**,src/bindings/** # do not consider test directory and Python bindings glue for coverage
 
 sonar.cfamily.reportingCppStandardOverride=c++17