similar to: R3.2.1: tools::testInstalledBasic("both") fails since no tests are installed by default. Confirmed?

Hello, I installed R 2.13.0 on a Windows 2003 server.? I downloaded the Rtools213.exe from http://www.murdoch-sutherland.com/Rtools/ and placed it in the path (C:\Program Files\R\R-2.13.0\bin). I submitted the following code: library(tools) Sys.setenv(LC_COLLATE=C) testInstalledBasic('basic') I get the following message in the R Console, which I believe corresponds to a failure of the

Hi, I'm currently in the process of writing an R-installation SOP for my company. As part of that process I'm using the recommendations from the 'R Installation and Administration' document, section 3.2, "Testing an installation". This is done on an XP machine, using the latest binary of 2.11.0. The binary is downloaded and then installed from the installer. I then

Dear users, I have a problem when using the testInstalledBasic function in the tools package on my windows 7 machine. I specified the environment variables as stated in the Installation and administration manual (Sys.setenv(LC_COLLATE = "C", LANGUAGE = "en")) and ran the function on an installation without additional packages. However the test fails on the script

I installed R on my Windows laptop in C:\Program 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

Hello. I've compiled R on Windows many times, and this is the first time I've seen this error. While running make check-all (and using testInstalledBasic("both")), the lm-tests routines fail, and, as far as I can tell, the diff is failing because in one file, answers are coming back like this "3.11e-004" while in the save file they are "3.11e-04". Every value

Hi, I am running R 2.13.0 on a Windows 7 machine. I ran the script: testInstalledBasic('devel') and received the following warning message: running tests of consistency of as/is.* creating ?isas-tests.R? running code in ?isas-tests.R? comparing ?isas-tests.Rout? to ?isas-tests.Rout.save? ...running tests of random deviate generation -- fails occasionally running code in

Hello. I am trying to build R on Windows. It appears that my build passes the various "make checks" (unless I missed some error) and running Rterm seems to work fine whereas Rgui has an immediate error stating " AppName: rgui.exe AppVer: 2.150.58871.0 ModName: rzlib.dll ModVer: 0.0.0.0 Offset: 0000a9e5 The taskbar still works, but the console window has nothing in it, and

>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: > Dear R developers > I think I have found a bug that can be reproduced with two lines of code > and I am very thankful to get your first assessment or feed-back on my > report. > If this is the wrong mailing list or I

Dear sir, For my statistical work I have installed R. But for analyzing an image in R I have to install jpeg packages. So I have to input command install.packages(?jpeg?). But error occurred: jpeglib.h file not found. What should I do? I use fedora 17.Please help me.

Dear Sr. of R-project: In the document "R: Regulatory Compliance and Validation Issues. A guidance Document for the Use of R in Regulated Clinical Trial Environments", in the point 6.3 say that exist a set of validation test, that are localized in the test subdirectory. I search the place in the page www.r-project.org and not found this, can you say me where is the set?. I work in a

On 23/02/2016 7:06 AM, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >> >> > Dear R developers >> > I think I have found a bug that can be reproduced with two lines of code

On 23.02.2016 14:06, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >> >> > Dear R developers >> > I think I have found a bug that can be reproduced with two lines of code >>

If I execute the code from the "?write.table" examples section x <- data.frame(a = I("a \" quote"), b = pi) # (ommited code) write.csv(x, file = "foo.csv", fileEncoding = "UTF-16LE") the resulting CSV file has a size of 6 bytes which is too short (truncated): """,3 The problem seems to be the iconv function:

Excellent analysis, thank you both for the quick reply! Is there anything I can do to get the bug fixed in the next version of R (e. g. filing a bug report at https://bugs.r-project.org/bugzilla3/)? On Tue, 2016-02-23 at 14:06 +0200, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: > >>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >

I am the author of the *tryCatchLog* package and want to - suppress selected conditions (warnings and messages) - rethrow selected conditions (e.g a specific warning as a message or to "rename" the condition text). I could not find any reliable unique identifier for each possible condition - that (base) R throws - that 3rd-party packages can throw (out of scope here). Is there any

On 24/02/2016 9:55 AM, Mikko Korpela wrote: > On 24.02.2016 15:47, Duncan Murdoch wrote: >> On 23/02/2016 7:06 AM, Mikko Korpela wrote: >>> On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >>>>

I have just committed your first patch (the strlen() replacement) to R-devel, and will soon put it in R-patched as well. I wont have time to look at this again before the 3.2.4 release, so your file.show() patch isn't going to make it unless someone else gets to it. There's still a faint chance that I'll do more in R-devel before 3.3.0, but I think it's best if there were bug

Thanks a lot for pointing out the reason (and yes, I am testing quite to stringent in this case - it's my old testing disease ;-) For other readers: The R-devel NEWS is a good source to find possible change reasons: https://stat.ethz.ch/R-manual/R-devel/doc/html/NEWS.html On Sun, 2019-09-29 at 08:33 -0400, Duncan Murdoch wrote: > On 29/09/2019 7:55 a.m., nospam at altfeld-im.de wrote:

Dear R friends, to allow post-mortem debugging In my Rscript based batch jobs I use tryCatch( <R expression>, error = function(e) { dump.frames(to.file = TRUE) }) to write the called frames into a dump file. This is similar to the method recommended in the "Writing R extensions" manual in section 4.2 Debugging R code (page 96):

Martin, thanks for the good news and sorry for wasting your (and others time) by not doing my homework and query bugzilla first (lesson learned! ). I have tested the new implementation from R-devel and observe a semantic difference when playing with the parameters: # Test script 1 g <- "global" f <- function(p) { l <- "local" dump.frames() }