Thanks for the help, I now tried resubmitting with
Sys.setenv("OMP_THREAD_LIMIT" = 2) at the top of the exchange example, but I
still get the same note:
Examples with CPU time > 2.5 times elapsed time
user system elapsed ratio
exchange 1.196 0.04 0.159 7.774
Not sure what to try n
In my case recently, after an hour or so’s messing about I disabled some
tests and example executions to get rid of the offending times. I doubt
that i am the only one to do that.
On Tue, 24 Oct 2023 at 9:38 pm, Helske, Jouni wrote:
> Thanks for the help, I now tried resubmitting with
> Sys.sete
В Tue, 24 Oct 2023 10:37:48 +
"Helske, Jouni" пишет:
> Examples with CPU time > 2.5 times elapsed time
> user system elapsed ratio
> exchange 1.196 0.04 0.159 7.774
I've downloaded the archived copy of the package from the CRAN FTP
server, installed it and tried:
library(bssm)
Chapter 15 in Wickham and Bryan, R Packages, discuss "Advanced
Testing Techniques". Their current section "15.4.1 Skip a test" includes
the following:
test_that("some long-running thing works", {
skip_on_cran()
# test code that can potentially take "a while" to run
})
Have you trie
On 24 October 2023 at 15:55, Ivan Krylov wrote:
| В Tue, 24 Oct 2023 10:37:48 +
| "Helske, Jouni" пишет:
|
| > Examples with CPU time > 2.5 times elapsed time
| > user system elapsed ratio
| > exchange 1.196 0.04 0.159 7.774
|
| I've downloaded the archived copy of the packag
You are not the only one; I did the same with some of my examples.
Would it be an option to ask for a default R-option, 'max.ncores', that
specifies the maximum number of cores a process is allowed to use? CRAN
could then require that that examples, tests and vignettes respect this
option. Tha
