similar to: timings for examples in R CMD check

Displaying 20 results from an estimated 3000 matches similar to: "timings for examples in R CMD check"

2023 Jul 02
1
Strange error in R CMD check --timings
This SO post: https://stackoverflow.com/q/76583828 describes a strange R CMD check error. Depending on the contents of a comment in one of the examples sections of a help page, an error like this could be triggered: > base::assign(".dptime", (proc.time() - get(".ptime", pos = "CheckExEnv")), pos = "CheckExEnv") >
2023 Jul 02
1
Strange error in R CMD check --timings
Am 02.07.23 um 18:01 schrieb Duncan Murdoch: > This SO post: https://stackoverflow.com/q/76583828 describes a strange R > CMD check error. Depending on the contents of a comment in one of the > examples sections of a help page, an error like this could be triggered: > > > base::assign(".dptime", (proc.time() - get(".ptime", pos = >
2007 Jul 04
1
Newbie creating package with compiled code
Hi R Gurus! I'm trying to create a test package using the package.skeleton function. I wanted to add some compiled code too. In the src library, I put together a baby subroutine, compiled it and created a test.dll When I use the R cmd build, it works fine. But I get into trouble with the R CMD check section. /home/Desktop/R-2.5.1/bin # ./R CMD check mypkg * checking for working latex ...
2006 Feb 15
1
S3 generics without NS and cleanEx()
Good morning, we recently observed a problem with importing S3 generics from a foreign package (without namespace), defining a S3 method in a package _with_ namespace and the `cleanEx()' function which is automatically generated and executed before examples are run by R CMD check. To be more precise. Package `strucchange' defines a S3 generic sctest <- function(x, ...)
2010 Apr 30
1
R package compilation in windows
dear R user, I al rying to compile an R package with some C code. everithing work fine as long as I work in Linux or MaCOX. unluckyly I can cant compile it under Windows, here is the error, but I cant figure it out what is the problem. can you help me? * using log directory 'C://MyPKG.Rcheck' * using ARGUMENT ' ' __ignored__ R version 2.11.0 (2010-04-22) * using session ARGUMENT
2013 Jan 30
1
R CMD check: Error in get("ptime", pos = "CheckExEnv") ...
Hi, Does anyboody have insight into what this error terminating "R CMD check" on an in-house package may imply? > ### > cat("Time elapsed: ", proc.time() - get("ptime", pos = 'CheckExEnv'),"\n") Error in get("ptime", pos = "CheckExEnv") : unused argument(s) (pos = "CheckExEnv") Calls: cat -> cat.default
2002 Mar 02
1
GNU tar does not ignore files in .Rbuildignore (PR#1339)
Full_Name: David O. Nelson Version: 1.4.1 OS: solaris 2.7 Submission from: (NULL) (128.115.150.74) Putting patterns in .Rbuildignore has no effect when the tar being used is gnu tar (1.13) on solaris 2.7, whilst /usr/sbin/tar works perfectly. TO REPRODUCE: The current directory contains a source package directory ./mypkg... bimini.jgi-psf.org% echo >mypkg/foo bimini.jgi-psf.org% echo
2008 Jan 22
3
gctorture and proc.time (PR#10600)
In R version 2.6.1 (2007-11-26) and R version 2.6.1 Patched (2008-01-19 r44061) on openSUSE 10.2 (X86-64) > gctorture() > proc.time() Error: protect(): protection stack overflow The problem with this is that then R CMD check --use-gct foo ALWAYS FAILS with > cat("Time elapsed: ", proc.time() - get("ptime", pos = 'CheckExEnv'),"\n") Error in
2011 Oct 18
1
cygwing warming when creating a package in windows
Dear All, I am a beginner creating R packages. I followed the Leisch (2009) tutorial and the document ?Writing R Extensions? to write an example. I installed R 2.12.2 (I also tried R2.13.2), the last version of Rtools and the recommended packages in a PC with Windows 7 Home Premium. I can run R CMD INSTALL linmod in the command prompt and the R CMD check linmod. The following outputs are
2009 Mar 05
1
problem building a package with C code (PR#13572)
Hi, my name is Paula. Im trying to learn how to build an R package in Windows XP using a simple example which includes a C source code. The foo.c file is located in mypkg/src/foo.c. I used the command Rcmd build --force --binary [pkgpath]. The problem is when I install the zip file in R the function foo doesn?t exist. The result a recieved during the building process is copied below. I really
2011 Oct 25
2
Building package/DESCRIPTION file not existing?
Hello useRs I am trying to build a package for personal use and for making easier working with other people but I keep getting the same error message about the DESCRIPTION file not existing. when trying to install from a source tar.gz file: Error in .read_description(dfile) : file 'C:/Users/PropriƩtaire/AppData/Local/Temp/RtmpHFMONb/R.INSTALL647a3535/mypkg/DESCRIPTION' does not
2005 Jun 19
1
Creating a R package for Windows XP
Hi: I'm trying to create a package to pass to someone else to use a group of functions with help files. I'm working on Windows XP. Step One: I use the example > ## two functions and two "data sets" : > f <- function(x,y) x+y > g <- function(x,y) x-y > d <- data.frame(a=1, b=2) > e <- rnorm(1000) > >
2004 Oct 28
2
Errors during make check
On a SUN 280R running Solaris 9... The configure and make steps completed without errors. But when I try to perform the make check step, I get the following: $ make check FORCE=FORCE `Makedeps' is up to date. running code in 'base-Ex.R' ...*** Error code 1 make: Fatal error: Command failed for target `base-Ex.Rout' Current working directory /usr/local/R-2.0.0/tests/Examples ***
2007 Jul 18
1
possible bug R CMD check: No space(s) allowed after \VignetteDepends{}
R CMD check gives an error when a vignette entry %\VignetteDepends{} has any extra space at the end. Maybe this is by design, but I found it confusing. Changing the function "vignetteMetaRE" in tools package could solve the problem. I.e. vignetteMetaRE <- function(tag) paste("[[:space:]]*%+[[:space:]]*\\\\Vignette", tag,"\\{([^}]*)\\}", sep = "")
2010 Apr 21
2
problem of R CMD check
Hi all, Today, i just installed the newest R version 2.10.1 and other necessary tools for building R package under windows,e.g. Rtools, perl. All are the newest version. After the correct configuration under windows, i use it to re-check my old package. I found the following prolem when checking EXAMPLE, which did not exist before this re-installation. ######## * checking examples ... ERROR
2005 Apr 22
1
Required Packages etiquette
Dear friends, I am writing a package that I think may be of interest to many people so I am in the process to build-check-write-thedocumentation for it. I have some questions regarding the "rules" that a package should abide in order to be consistent with the other packages on CRAN. I have read and reread the Writing R extension manual and googled the mailing list and I have found
2006 Nov 16
2
trouble loading example package
Greetings: I've installed Rtools, MikTeX, perl, minGW, and HTML Help Workshop, and have succeeded in making, checking (using R CMD check mypkg) then building the simple example package.skeleton(list=c("f","g","d","e"), name="mypkg") R CMD build mypkg produces a tarball. I don't know how to get a zip file. But when I try to Install
2007 Jun 05
1
'R CMD INSTALL mypkg' doesn't always update help pages
Hi, 'R CMD INSTALL mypkg' and 'install.packages(mypkg, repos=NULL)' don't update mypkg help pages when mypkg is a source directory. They only install new help pages if there are some but they leave the already installed pages untouched. So you end up with mixed man pages from different versions of the package :-/ I found no mention of this in 'R CMD INSTALL --help' or
2005 May 14
1
make check fails after building R 2.1.0 on Fedora Core 3
I have R v2.0.1 already running on the machine in question; a fairly generic Fedora Core 3 machine. I am trying to build the new version 2.1.0 and have not been able to troubleshoot the problem I encountered. I'm hoping someone else has seen it and can suggest a troubleshooting avenue to me. The build succeeds, both from the source RPM and from the tarball. I believed I had all the build
2010 Sep 06
1
How to get "mypkg-manual.pdf"
I am building a package say mypkg. Five months ago, when I built the package I got the mypkg manual in pdf format. Today, after making updates, I build the same package, same name, and steps; unfortunately I do not get the manual in pdf format. Rather I get the following message: cd: can't cd to /cygdrive/c/Documents saving output to 'mypkg-manual.pdf' ...Done Could any one