[
https://issues.apache.org/jira/browse/IMPALA-13279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871519#comment-17871519
]
ASF subversion and git services commented on IMPALA-13279:
----------------------------------------------------------
Commit ed94f31a25de86ef768d98fd3e4a27e0aedc5cca in impala's branch
refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=ed94f31a2 ]
IMPALA-13279: Upgrade gcovr to 7.2
In some environments, the code coverage report is empty even
though the tests ran successfully and gcno/gcda files are
written properly.
This upgrades to gcovr 7.2, which does not show the same
problem. gcovr 7.2 requires Python 3.8, so this switches to use
Python 3.8 from the toolchain and installs gcovr in the Python 3
virtualenv.
gcovr 7.2 outputs logging to stderr, so this also modifies
bin/coverage_helper.sh to redirect stderr to stdout.
Testing:
- Verified that this can generate a report locally and on
the affected environment
Change-Id: I5b1aaa92c65f54149a3e7230cbe56d5286f1051a
Reviewed-on: http://gerrit.cloudera.org:8080/21647
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> In some environments, code coverage produces an empty report
> ------------------------------------------------------------
>
> Key: IMPALA-13279
> URL: https://issues.apache.org/jira/browse/IMPALA-13279
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 4.5.0
> Reporter: Joe McDonnell
> Priority: Major
>
> On some environments used for automation, all the tests run with code
> coverage enabled but the report at the end is empty. Impala is generating the
> necessary gcno/gcda files on exit, so this seems to be a bug during report
> generation in that environment. It works fine locally on my Ubuntu 20
> development box, so there is something special about the environment.
> Testing with the latest version of gcovr (7.2) doesn't show the same issue,
> so one path to fixing this is to upgrade to gcovr==7.2. gcovr 7.2 requires
> python 3.8, so it would involve switching to the toolchain 3.8 python rather
> than the 3.7 python.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
