[
https://issues.apache.org/jira/browse/ARROW-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539492#comment-17539492
]
Antoine Pitrou commented on ARROW-15768:
----------------------------------------
But to answer your other question, yes, we could extend this to all components.
It's just probably easier to do it piecewise.
> [CI][C++] Reinstate a code coverage job
> ---------------------------------------
>
> Key: ARROW-15768
> URL: https://issues.apache.org/jira/browse/ARROW-15768
> Project: Apache Arrow
> Issue Type: Task
> Components: C++, Continuous Integration
> Reporter: Antoine Pitrou
> Priority: Major
>
> Long ago we used to have code coverage measured on our Travis-CI setup. We
> dropped it because it was difficult to maintain and also a bit costly in
> additional execution time AFAIR.
> Now that we have nightly builds using Crossbow and the flexibility of Github
> Actions workflows (where we could even perhaps run coverage on e.g. Linux and
> Windows, then combine the files as a final merge job), we should be able to
> create a new code coverage job.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
