[
https://issues.apache.org/jira/browse/ARROW-12143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310967#comment-17310967
]
Neal Richardson commented on ARROW-12143:
-----------------------------------------
We use the {{rcmdcheck}} package to run the package checks, and it runs them in
a subprocess. There is a "timeout" arg we can set:
https://github.com/r-lib/rcmdcheck/blob/master/R/package.R#L36
Unclear what output is available to be captured if it is killed at the timeout,
but we can try and surely can submit a PR to {{rcmdcheck}} if necessary.
> [CI] R builds should timeout and fail after some threshold and dump the
> output.
> -------------------------------------------------------------------------------
>
> Key: ARROW-12143
> URL: https://issues.apache.org/jira/browse/ARROW-12143
> Project: Apache Arrow
> Issue Type: Improvement
> Components: CI, R
> Reporter: Weston Pace
> Priority: Major
>
> Currently, if an R test hangs, then it is very difficult to determine what
> the root cause is because it just outputs "checking tests". It also slows
> down the CI pipeline because it doesn't time out for 6 hours.
> I'm hoping we can instead kill the test after some unreasonable amount of
> time has passed and dump whatever output has been generated so far.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
