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
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.
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:
Note: This issue was originally created as ARROW-12040. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: