[
https://issues.apache.org/jira/browse/ARROW-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306493#comment-17306493
]
Neal Richardson edited comment on ARROW-12040 at 3/22/21, 6:39 PM:
-------------------------------------------------------------------
Unfortunately we can't make `R CMD check` more verbose. We can make the test
output, which is redirected to a file by `R CMD check`, more verbose, and we
have an option in our Windows CI for doing that:
[https://github.com/apache/arrow/blob/master/.github/workflows/r.yml#L160-L168]
But that won't help debugging the failure on Azure because the check is
hanging, so I don't think the build artifact will be generated in a way you
could get it. But since this is a docker-compose job, one could do it
locally/interactively and perhaps get some insight.
was (Author: npr):
Unfortunately we can't make `R CMD check` more verbose. We can make the test
output, which is redirected to a file by `R CMD check`, more verbose, and we
have an option in our Windows CI for doing that:
[https://github.com/apache/arrow/blob/master/.github/workflows/r.yml#L160-L168]
That won't help debugging the failure on Azure because the check is hanging, so
I don't think the build artifact will be generated in a way you could get it.
But since this is a docker-compose job, one could do it locally/interactively
and perhaps get some insight.
> [R] [CI] test-r-rstudio-r-base-3.6-opensuse15 timing out during tests
> ---------------------------------------------------------------------
>
> Key: ARROW-12040
> URL: https://issues.apache.org/jira/browse/ARROW-12040
> Project: Apache Arrow
> Issue Type: Improvement
> Components: CI, R
> Reporter: Jonathan Keane
> Priority: Major
>
> The nightly job test-r-rstudio-r-base-3.6-opensuse15 has timed out on tests
> for (at least) the last 3 nightly jobs now.
> Everything seems fine until the `checking tests ...` stage of R CMD CHECK
> which hangs for long enough that Azure kills the job because the total job
> has exceed 360 minutes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
