Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Refactor gcov parsing code, support upcoming GCC 8 changes #228
This PR refactors the
The changes to support the upcoming GCC 8 were made in response to #226. The new gcov report format gets new sections that report coverage individually for each template or macro specialization. This PR does not support them, but merely strips away the section delimiters. The result is that branches are parsed for such lines, but I'm not sure how coverage from multiple sections on the same line is combined.
To prevent future problems like this, the parsing code was made more “robust”. The
So there's still a lot that can be improved with regards to gcov parsing and logging, but this is a start.
@@ Coverage Diff @@ ## master #228 +/- ## ======================================== + Coverage 84% 87.5% +3.5% ======================================== Files 11 12 +1 Lines 1194 1337 +143 Branches 248 240 -8 ======================================== + Hits 1003 1170 +167 + Misses 131 116 -15 + Partials 60 51 -9
Is Python 2.6 still needed? It's been EOL for over 4 years and is no longer receiving security updates.
It's also little used. Here's the pip installs for gcovr from PyPI for last month:
(Python 3.3 is also EOL not listed here, how about dropping that too?)