Hello G Ann,
Thanks for the reply. But this still leaves the question unanswered. I get that executable line analysis is the reason that SonarQube is doing this and an acceptable default behavior but when one provides LCOV report it means we don’t want sonarQube to be extra smart and just use the provided LCOV report. Simply put given an LCOV report SonarQube should respect it without trying to do extra.
But if SonarQube want to enforce the executable line analysis then at least display 2 coverage reports to make things little clear with one showing coverage from LCOV and then one with Executable lines logic.
Further, there should be a way to turn that feature off, so that it respects LCOV report as is.