[R-pkg-devel] CRAN pre-test failure due to long runtime / timeout

[Dirk Eddelbuettel]

On 22 July 2022 at 21:09, Jonas Kurle wrote:
| The automatic CRAN pre-tests fail and it seems that this is due to 
| runtime timeout (in the tests). For Windows, I get the message "Check 
| process probably crashed or hung up for 20 minutes ... killed" and for 
| Debian, I get "checking tests ... [30m/30m] ERROR". See below for the 
| links to the log files.

[...]

| Can anyone advise me what to do?

There is a "fix" addressing the _symptom_ but not the _cause_: simply do not
run the tests. Your time is finite, CRAN maintainer time is certainly finite.
Even today we still do not have a real ability to cleanly reproduce CRAN
checks (win-builder is pretty close, but eg CRAN Debian is not Dockerized and
hence not really reproducible (I once offered help but this petered out
without generating anything tangible).

This topic has been discussed a few times before. Some people advocate using
skip_on_cran() (if you use testthat). I don't testthat but in some packages
only run tests if an env. var is set which I set eg for GitHUb Actions.

Hth, Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | edd using debian.org