[R-pkg-devel] R CMD check yielding different results for me than CRAN reviewer
The most common scenario is that you're using R-release and the warnings are coming from the R-devel version, which often has a bunch of new, additional tests. The other frequent answer to this question (is there a FAQ list for this mailing list yet?) is that using CRAN's win-builder service is a very easy way to get access to the R-release and R-devel tests without changing anything in your local setup.
On Tue, Jan 26, 2016 at 2:03 PM, Adah Zhang <asz25 at case.edu> wrote:
Hello,
I am running R CMD check (and also with the --as-cran flag), which results
in all OK's in my 00check.log. However, after submitting the package, the
CRAN reviewer tells me of a warning/error regarding one of my examples
(which is easily fix-able if I got the warning myself).
How do I ensure that all warnings, errors, and notes are addressed if I do
not receive these when running the standard checks or when testing the
examples myself? Is there a standard order of commands that a CRAN reviewer
goes through aside from 'R CMD check'?
Thanks,
Adah
[[alternative HTML version deleted]]
______________________________________________ R-package-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel