You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2021/10/29 10:40:00 UTC
[jira] [Resolved] (IMPALA-10899) buildall.sh -release_and_debug
-codecoverage doesn't work as expected
[ https://issues.apache.org/jira/browse/IMPALA-10899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltán Borók-Nagy resolved IMPALA-10899.
----------------------------------------
Fix Version/s: Impala 4.1.0
Resolution: Fixed
> buildall.sh -release_and_debug -codecoverage doesn't work as expected
> ---------------------------------------------------------------------
>
> Key: IMPALA-10899
> URL: https://issues.apache.org/jira/browse/IMPALA-10899
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: newbie, ramp-up
> Fix For: Impala 4.1.0
>
>
> If the user issues "buildall.sh -release_and_debug -codecoverage", the script will do a releae build, then a debug build, without generating any code coverage data:
> https://github.com/apache/impala/blob/beb8019f5300bb163424e7fdfec50b8e4b796e26/buildall.sh#L607
> We cannot really generate code coverage information for both release and debug builds because the second build overwrites the cmake directories, hence it overwrites the .gcno files as well.
> Therefore we should raise an error when the use specifies both -release_and_debug and -codecoverage. Another workaround could be to copy the .gcno files to a directory after the builds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org