search for: check_packag

...quot;) } Notice the "|" instead of "||". I can't see how this would lead to the issue you saw, but it should be fixed. It's not easy to say what --as-cran does, other than to look at the function that implements R CMD check. That function is the huge tools:::.check_packages. You can run it in an R session using options(warn = 2, error = recover) tools:::.check_packages(c("--as-cran", "coxme_2.2-14.tar.gz")) When I do that I get a different error report; it reports this test instead: if(class(varlist) == "coxmevar") That a...

...r *** caught segfault *** address 0x7fff6073c998, cause 'memory not mapped' Traceback: 1: file.copy(pkgdir, vd2, recursive = TRUE) 2: run_vignettes(desc) 3: check_pkg(pkgdir, pkgname, pkgoutdir, startdir, libdir, desc, is_base_pkg, is_rec_pkg, thispkg_subdirs, extra_arch) 4: tools:::.check_packages() aborting ... Segmentation fault (core dumped) as one can see, the error stems from the call file.copy(pkgdir, vd2, recursive = TRUE) in the run_vignettes function defined in the tools:::.check_packages function. this call will copy the contents of "pkgdir" (the source directory) to t...

...ually aren't.) Alternatively (or maybe additionally), it may be possible to enhance the R CMD check diagnostics by checking whether the name of the undocumented object starts with a dot and asking the user whether it was intended to be exported. This is not as easy to implement due to tools:::.check_packages working with the log output from tools::undoc(), not the object itself. Would a change to tools:::format.undoc be warranted? -- Best regards, Ivan

Dear all, i contact you for an issue I encountered after a little time I didn't developed/checked packages at work. The issue I have is from R CMD check: > tools:::.check_packages() * using log directory ?/home/l/src/rpkg/lbmisc.Rcheck? * using R version 3.3.2 (2016-10-31) * using platform: x86_64-pc-linux-gnu (64-bit) * using session charset: UTF-8 * using options ?--no-build-vignettes --as-cran? * checking for file ?lbmisc/DESCRIPTION? ... OK * this is package ?lbmisc? v...

...iles under 'inst/doc' ... NOTE Unable to find GhostScript executable to run checks on size reduction Setting 'R_GSCMD' to "gswin32c.exe" and asserting that it is the PATH (this is on Windows), it works. TROUBLESHOOTING: In the local function check_doc_size() of tools:::.check_packages() [cf. http://svn.r-project.org/R/trunk/src/library/tools/R/check.R], the Ghostscript executable is retrieved as: gs_cmd <- find_gs_cmd(Sys.getenv("R_GSCMD", "")) and if nzchar(gs_cmd) is FALSE, then the 'R CMD check' NOTE appears. Inspecting tools:::find_gs_cmd,...

...s 0x7fff6073c998, cause 'memory not mapped' > > Traceback: > ?1: file.copy(pkgdir, vd2, recursive = TRUE) > ?2: run_vignettes(desc) > ?3: check_pkg(pkgdir, pkgname, pkgoutdir, startdir, libdir, desc, > is_base_pkg, is_rec_pkg, thispkg_subdirs, extra_arch) > ?4: tools:::.check_packages() > aborting ... > Segmentation fault (core dumped) > > as one can see, the error stems from the call > file.copy(pkgdir, vd2, recursive = TRUE) > in the run_vignettes function defined in the tools:::.check_packages > function. this call will copy the contents of "pkgdir...

Where can I find out (and replicate) what options as-cran turns on? The issue: the following lines generate an error in R CMD check --as-cran? for coxme.? But there is no error without as-cran nor is there one when I run the code in a terminal window. ismat <- function(x)? inherits(x, "matrix") || inherits(x, "bdsmatrix") || inherits(x, "Matrix") if

I have created a quite minimal package with a simple R program in the tests subfolder. When I run CMD check, I get * checking examples ... OK * checking for unstated dependencies in tests ... OK * checking tests ...sh: : No such file or directory ERROR I don't see a way of diagnosing this. The content of tests is the program t1.R rex-bash-3.2$ cat t1.R date() On other machines I can

...ROR Re-running with no redirection of stdout/stderr. The workaround is as simple as using -o to redirect the output to a sane path. This could be just a case of "don't do this", but I wanted to save some future problem-Googler 10 minutes of digging around in the guts of .tools:::check_packages() to find out what was going on ... I don't know whether this is technically a bug or not. Presumably something could be tweaked in check_pkg_manual() within src/library/tools/R/check.R to protect parentheses in the shell argument string ... Ben Bolker

...did svn update and tools/rsync_recommended earlier today and it didn't fix the issue. Specifically, it is hanging on the * checking dependencies in R code ... stage (while checking Matrix, it passes fine for MASS and lattice). Currently I'm getting the same behavior when I do tools:::.check_packages("<builddir>/tests/RecPackages/Matrix") Is this a known issue and if not, do other people see this behavior? Best, ~G Various info: Build script: #!/bin/bash export CC="gcc -std=gnu99 -fsanitize=address" # make -O0 if we want full debugging symbols export CFLAGS=&...

Is the mechanism by which packages are tested on CRAN described anywhere? Is it by any chance written in R? The FastR <https://bitbucket.org/allr/fastr/wiki/Home> team is interested in running a virtual CRAN where we can test all the CRAN packages on FastR. Thanks Mick Jordan [[alternative HTML version deleted]]