-
Notifications
You must be signed in to change notification settings - Fork 2
Description
recheck of "terra" with strong dependencies gets cancelled after 6 hours and a bit. See this one from yesterday. (It is a bit hard to inspect because installing package nimble created 30,000 lines of warnings!) I deleted earlier failed attempts. I think this happens because of the 6 hours limit on job execution time for a GitHub-hosted runner.
terra currently has 362 reverse dependencies and it the processing speed is about 50-60 packages per hour.
To circumvent this problem I added options "Depends" and "Imports" to the "which dependents to check" select box, and I was able to run both in separate runs. So for now I am good, but "Imports" has 92% (333/362) of the packages and it took 6:02 hrs to check these. So this is likely to also fail soon as the number of reverse dependencies increases, and also to fail for other packages with many rev deps and/or with long check times.
I think this problem could be circumvented by adding an option to subset the packages to be checked, using a grep pattern (something like this). A value like ^[a-k] could be passed to rechecktools::install_recheck_deps where something like this could be done: if (trimws(pattern != "")) packages <- grep(pattern, packages, value=TRUE, ignore.case=TRUE).
Allowing this option could also be practical to more quickly identify a problem and to recheck a set of reverse dependencies that reported a new error/warning in a previous run.