Hello.
As already pointed out, the current R implementation treats any
non-empty value on _R_CHECK_LIMIT_CORES_ different from "false" as a
true value, e.g. "TRUE", "true", "T", "1", but also "donald duck".
Using '--as-cran' sets _R_CHECK_LIMIT_CORES_="TRUE", if unset. If
already set, it'll not
Hi Ivan,
thanks for the info, I changed the check as you pointed out and it
worked. R CMD build and R CMD check --as-cran run without errors or
warnings on Linux + MacOS. However, I uploaded the package again at the
WINBUILDER service and obtained the following weird error:
* checking
В Wed, 16 Nov 2022 07:29:25 +0100
Riko Kelter пишет:
> if (nzchar(chk) && chk == "TRUE") {
> # use 2 cores in CRAN/Travis/AppVeyor
> num_workers <- 2L
> }
The check in parallel:::.check_ncores is a bit different:
chk <- tolower(Sys.getenv("_R_CHECK_LIMIT_CORES_", ""))
if (nzchar(chk) && (chk
Hello,
I have a short question on the number of processes which are spawned
during parallelization. My package passes R CMD check –as-cran on MacOS
and Linux, but the vignettes fail with the following error on Windows
and Debian:
|--- re-building 'gettingstarted.Rmd' using rmarkdown Quitting
