[R] [CI] [C++] test-r-rstudio-r-base-3.6-opensuse15 timing out during tests

[asfimport]

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.

Reporter: Jonathan Keane / @jonkeane
Assignee: Weston Pace / @westonpace

PRs and other links:

• GitHub Pull Request #9842

_{Note: This issue was originally created as ARROW-12040. Please see the migration documentation for further details.}

[asfimport]

Jonathan Keane / @jonkeane:
One example of the failure point: https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=2280&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=234

[asfimport]

Antoine Pitrou / @pitrou:
It would be very nice if you could find a way to make the "checking tests" step verbose by default (at least on CI). This kind of annoyance has happened more than once.

[asfimport]

Neal Richardson / @nealrichardson:
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.

[asfimport]

Jonathan Keane / @jonkeane:
When reproducing locally, the tests hang on https://github.com/apache/arrow/blob/master/r/tests/testthat/test-s3-minio.R#L116 ds <- open_dataset(fs$path(minio_path("hive_dir")))

[asfimport]

Antoine Pitrou / @pitrou:
Issue resolved by pull request 9842
#9842