Re: [R-pkg-devel] \donttest{} and writing outputs to tempdir()

2021-06-01 Thread Jeff Newmiller
Make examples shorter so they can run faster. Wrapping everything in donttest means that running examples() does nothing, which is counterproductive. Techinically, vignettes are not tests or examples... but they do have the advantage that they don't have to run quickly. But that doesn't make a v

Re: [R-pkg-devel] \donttest{} and writing outputs to tempdir()

2021-06-01 Thread Hugh Parsonage
Are you able to provide a link to your package? It's a bit hard to guess what's causing your examples etc to have these problems. On Wed, 2 Jun 2021 at 14:40, Danielle Maeser wrote: > > Hello, > > I received the following comments from a CRAN maintainer, and I don't > understand why they were an

[R-pkg-devel] \donttest{} and writing outputs to tempdir()

2021-06-01 Thread Danielle Maeser
Hello, I received the following comments from a CRAN maintainer, and I don't understand why they were an issue. I'd appreciate any insight you can provide. Danielle *All your examples are wrapped in \donttest{} and therefore do not gettested.Please unwrap the examples if that is feasible a

[R-pkg-devel] Valgrind warning: invalid size of 4, is it due to a simple overrun?

2021-06-01 Thread Hugh Parsonage
Hello, I received a valgrind warning about my package, hutilscpp, from CRAN (thank you). I believe I've tracked down and fixed the problem, but I wasn't able to reproduce the error on rhub (including with --leak-check=full etc) so I'd like to know if I'm missing something. The valgrind warning i