You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Jacob Wujciak-Jens (Jira)" <ji...@apache.org> on 2022/04/06 18:10:00 UTC

[jira] [Assigned] (ARROW-15015) [R] Test / CI flag for ensuring all tests are run?

     [ https://issues.apache.org/jira/browse/ARROW-15015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacob Wujciak-Jens reassigned ARROW-15015:
------------------------------------------

    Assignee: Jacob Wujciak-Jens

> [R] Test / CI flag for ensuring all tests are run?
> --------------------------------------------------
>
>                 Key: ARROW-15015
>                 URL: https://issues.apache.org/jira/browse/ARROW-15015
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: R
>            Reporter: Jonathan Keane
>            Assignee: Jacob Wujciak-Jens
>            Priority: Major
>
> We frequently skip [tests that depend on features that are not available|https://github.com/apache/arrow/blob/b9ac245afef081339093cd1930153d6b18b0479d/r/tests/testthat/helper-skip.R#L24-L34] which is nice (especially for CRAN tests, where the features might not be buildable.
> But should we have a CI flag that we could turn on (that is, off by default) that forces all of these tests to be run so we can know there is at least one build that runs all the tests? AFAICT, right now if we have no CI that successfully builds parquet, for example, most of our parquet tests would silently not run.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)