Hi Guido, Yes \dontrun works fine for me as well when I'm running the package check on my own, as well as the win-builder link you've sent. The problem I always run into is that when it first gets inspected by CRAN it is always flagged and I am asked to change \dontrun to \donttest, or remove \dontrun completely. I'm not sure if there is a way for me to avoid that.
Best, Martin On Tue, Nov 16, 2021 at 12:56 PM Guido Schwarzer <s...@imbi.uni-freiburg.de> wrote: > Am 16.11.21 um 20:16 schrieb Martin Ondrus: > > > Hi Duncan, > > > > That's a fair point, and I think making the examples run quicker probably > > makes the most sense. I have bad experiences with using dontrun - my > > package always gets flagged. Although not ideal, it's probably better to > > include some very fast running examples rather than none at all. > Appreciate > > your advice/help! > > I have been using dontrun for a long time (and I am still using it) > without any real issues. Initially, I used it to get rid of runtime > notes impeding submission to CRAN. Now I am also using it for additional > features, e.g., to describe some additional analyses / figure layouts. > > I always check my packages under R-devel on > https://win-builder.r-project.org/ before submission to CRAN. If this > does not trigger any notes, the package is good to go. > > Best, Guido > > [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
