Among other tests, CRAN uses the development version of R (R-devel) for
checks. It usually contains more stringent tests than the release
version of R, so possibly you were using a release version for tests and
that test wasn't in it.
The Github action r-lib/actions/check-r-package@v2 will run on R-devel
if you specify "r: 'devel'". For example in my rgl package checks
(visible at
https://github.com/dmurdoch/rgl/blob/master/.github/workflows/R-CMD-check.yaml),
I check on the release and the devel versions by having
matrix:
config:
- {os: windows-latest, r: 'release'}
- {os: windows-latest, r: 'devel'}
- {os: ubuntu-latest, r: 'devel', http-user-agent: 'release'}
- {os: macos-latest, r: 'devel'}
Duncan Murdoch
On 2025-07-10 6:13 a.m., Ghislain Durif wrote:
Hi,
I am the maintainer of a package for which we have done a major
refactoring (work in progress, can be found here
<https://github.com/getkeops/keops/tree/fix_rkeops_v2_keops_v2.3/rkeops>).
Upon my last resubmission to CRAN, some issues regarding some man pages
(that I obviously missed) were found, e.g. function doc without a
\value{} tag, or examples for (purposely) unexported functions.
These issues were not raised during package check (with or without
`--as-cran` flag).
The code base is quite large, and I would be very interested in any tool
that could help me check the man pages more thoroughly than a package
check ?
I know about `devtools::check_man()` but it does not find the issues
that I am mentioning.
Thanks in advance,
Best regards,
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
