On 13.08.2023 08:14, Ivan Krylov wrote:
В Sat, 12 Aug 2023 22:49:01 -0700
Michael Topper пишет:
It appears that some of my examples/tests are taking too
long to run for CRAN's standards.
I don't think they are running too long; I think they are too parallel.
The elapsed time is below 1s,
В Sat, 12 Aug 2023 22:49:01 -0700
Michael Topper пишет:
> It appears that some of my examples/tests are taking too
> long to run for CRAN's standards.
I don't think they are running too long; I think they are too parallel.
The elapsed time is below 1s, but the "user" time (CPU time spent in
the
Hello all,
Not sure how to handle this, as it had not been an issue on my previous
CRAN submissions. It appears that some of my examples/tests are taking too
long to run for CRAN's standards. Is there a way around this other than the
simple "change the example" or "change the test"?
Moreover, is
On 12.08.2023 23:19, Dirk Eddelbuettel wrote:
On 12 August 2023 at 18:12, Uwe Ligges wrote:
| On 12.08.2023 15:10, Jamie Lentin wrote:
| > The system call in question is done by the TMB package[2], and not ours
| > to tinker with:
| >
| > cmd <- paste("R --vanilla < ",file," -d gdb --debug
On 12 August 2023 at 18:12, Uwe Ligges wrote:
| On 12.08.2023 15:10, Jamie Lentin wrote:
| > The system call in question is done by the TMB package[2], and not ours
| > to tinker with:
| >
| > cmd <- paste("R --vanilla < ",file," -d gdb --debugger-args=\"-x",
| > gdbscript,"\
On 12.08.2023 15:10, Jamie Lentin wrote:
Hello list,
Our package gadget3[0] has just started failing the "donttest"
additional check[1] on r-devel-linux-x86_64-fedora-gcc, specifically:-
> # Build the model in an isolated R session w/debugger
> writeLines(TMB::gdbsource(g3_tmb_adfun(
Hello list,
Our package gadget3[0] has just started failing the "donttest"
additional check[1] on r-devel-linux-x86_64-fedora-gcc, specifically:-
> # Build the model in an isolated R session w/debugger
> writeLines(TMB::gdbsource(g3_tmb_adfun(cpp, compile_flags = "-g",
output_script = TRU
