search for: testinstalledpackage

Hello, I'm writing a script that automates the testing of reverse dependencies of a package. I found the function testInstalledPackage in the tools package, which seems to do what I want. However, when I use it for a source package that was installed with --install-tests, I've noticed that only the actual test files (e.g. located in inst/tests) are available and run. In other words the test harness script (e.g. in tests) is no...

Background: I run tools::testInstalledPackage on all packages that dependend on survival (605 as of today) before sending a new release to CRAN. It has a few false positives which I then follow up on.? (Mostly packages with as-yet-incomplete tests in their inst directory). ?Issue: testInstalledPackage("mets")? generates an? &quot...

...am Files\R\R-2.15.2 and am able to open RGUI (640bit), see packages and run commands. However, when I test the installation and run the basic tests and all the tests on the standard and recommended packages i.e.: library("tools") testInstalledBasic("both") testInstalledPackages("base", errorsAreFatal = FALSE) testInstalledPackages("recommended", errorsAreFatal = FALSE) I am getting errors such as: > testInstalledPackages("base",errorsAreFatal=FALSE) Error in setwd(outDir) : cannot change working directory my working driec...

Dear group, ? When running the installation test: ? testInstalledPackages("both",outDir='c:/Test') ? I got the following message: Running ?testci.R? comparing ?testci.Rout? to ?testci.Rout.save? ... files differ in number of lines: Please note the test does not result in 'OK' as do the other tests.? Is this a concern? Regards, ???-Cody Hamil...

I installed R version 2.15.0 under C:/ on a PC running Windows 7.  When I load library("tools") to test the installation and then run the command testInstalledPackages("base"), I get the following error: Error in setwd(outDir): cannot change working directory. I have set up the R shortcut to run it as administrator. [[alternative HTML version deleted]]

..._STDC__ -D__EXTENSIONS__ " in config.site. There's a bit of weirdness about what the starting directory is if one follows the instructions at the bottom of page 8. It *really* cared what PWD was when I invoked R. Starting R in the wrong place caused setwd(outDir) to fail when I invoked testInstalledPackages("base"). Apparently because R.home() was not prepended to the package name when forming outDir. However, I'm not entirely sure of that even though I sort of got things to run by doing a "find . -name base" and moving around before starting R. Once I got testInstalledPac...

...ompile the vignette. Installing rmarkdown should solve > the problem. If not, please provide more information. OS, R version, > digest version, ... > > This is occurring in the context of an automated testing environment that compares the output of GnuR and FastR. I'm using tools::testInstalledPackage with the default values for 'types'. I guess the problem is that there is no connection between this step and the previous package install step (that did use --install-tests) but didn't install the "Suggests" dependencies because in general these are not needed. But I stil...

...talling rmarkdown should solve >> the problem. If not, please provide more information. OS, R version, >> digest version, ... >> >> > This is occurring in the context of an automated testing environment that > compares the output of GnuR and FastR. I'm using tools::testInstalledPackage > with the default values for 'types'. I guess the problem is that there is no > connection between this step and the previous package install step (that did > use --install-tests) but didn't install the "Suggests" dependencies because > in general these are not ne...

I'm testing a new release of survival, executing the following piece of code: .... for (testpkg in survdep) { z <- testInstalledPackage(testpkg, outDir="tests") cat(testpkg, c("Ok", "Failed")[z+1], "\n", file="progress", append=T) } The vector survdep contains the names of all 156 packages listed as reverse depends on the CRAN page for survival. All works well except for the...

I need some help understanding a problem running the tests on the 'digest' package. Initially, I got the message that the 'knitr' package was needed to run vignettes: Running vignettes for package ?digest? Error in loadVignetteBuilder(vigns$pkgdir) : vignette builder 'knitr' not found So I installed the knitr package and all its dependents (?mime?, ?stringi?,

...reported error context, and include the filename and line and column numbers so smart text editors can jump to the error location. o str(<1d-array>) now writes "[1:n(1d)]" instead of the previous less clear "[, 1:n]". o New function testInstalledPackage() in package 'tools' allows the examples (and if they were installed) any package-specific tests to be run on an installed package. testInstalledPackages() can run all the examples and tests in the standard and/or recommended packages. Also testInst...

...reported error context, and include the filename and line and column numbers so smart text editors can jump to the error location. o str(<1d-array>) now writes "[1:n(1d)]" instead of the previous less clear "[, 1:n]". o New function testInstalledPackage() in package 'tools' allows the examples (and if they were installed) any package-specific tests to be run on an installed package. testInstalledPackages() can run all the examples and tests in the standard and/or recommended packages. Also testInst...

Below is the output. Thanks for the help. > Sys.getenv() BASH_FUNC_module() () { eval `/cm/local/apps/environment-modules/3.2.10/Modules/$MODULE_VERSION/bin/modulecmd bash $*` } COLUMNS 152 CPATH /cm/shared/apps/uge/8.2.1/include CVS_RSH ssh DISPLAY localhost:10.0 EDITOR

...1 When I compare the isas-tests.Rout to isas-tests.Rout.save, as well as the two diff files listed above, it seems that there is one extra empty line in isas-tests.Rout.save. Is there any way to fix this error without modifying the isas-tests.Rout.save file? Next I submitted the following code, testInstalledPackages(scope="base") and got the message below in my R console: > testInstalledPackages(scope="base") Testing examples for package ?base? Testing examples for package ?tools? comparing ?tools-Ex.Rout? to ?tools-Ex.Rout.save? ... 621c621 < [1] "0cce1e42ef3fb133940946534fc...

...dered PDF and plain-text help. In code blocks, pure comment lines (starting with %) no longer produce an empty line. * xtabs(Freq ~ .) now consistently defaults to na.action = na.pass, using na.rm = FALSE (added as an argument) when summing over Freq (PR#17770). * tools::testInstalledPackage() is no longer silent about failures from running examples or tests and its return code no longer ignores failures from checking vignettes. -- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)3815350...

...dered PDF and plain-text help. In code blocks, pure comment lines (starting with %) no longer produce an empty line. * xtabs(Freq ~ .) now consistently defaults to na.action = na.pass, using na.rm = FALSE (added as an argument) when summing over Freq (PR#17770). * tools::testInstalledPackage() is no longer silent about failures from running examples or tests and its return code no longer ignores failures from checking vignettes. -- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)3815350...