[
https://issues.apache.org/jira/browse/ARROW-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539830#comment-17539830
]
Jacob Wujciak-Jens commented on ARROW-15768:
--------------------------------------------
Yes I agree that doing it piecewise would be the right choice and that creating
an umbrella issue for that with this as a subtask would be the way to go. But I
am whole unfamiliar with any code coverage systems outside of R's testthat &
codecov (where you just run the test suit again to collect the data which takes
marginal time compared to compiling libarrow) so I will have to look into this
before committing to anything :)
> [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)
