Re: [Rd] Strange error in R CMD check --timings

On 02/07/2023 2:34 p.m., Sebastian Meyer wrote: 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

Re: [Rd] 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", (pro

[Rd] 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"))

Re: [Rd] Strange error messages from parallel::mcparallel family under 3.6.0

Thanks, fixed in R-devel and R-patched. The error happens in the child process when it is already exiting, after it had delivered a result, so this should not cause any trouble in an unpatched version of R (apart from showing that message). It is specific to mccollect(wait=FALSE). Best Tomas

[Rd] Strange error messages from parallel::mcparallel family under 3.6.0

Dear All, Since upgrading to 3.6.0, I've been getting a strange error messages from the child process when using mcparallel/mccollect. Before filing a report in the Bugzilla, I want to figure out whether I had been doing something wrong all this time and R 3.6.0 has exposed it, or whether someth

[Rd] Strange error

Someone just sent me a data set that causes the lmekin function, part of the kinship package, to fail. In chasing it down I get an error I have never seen before. fit <- lmekin(icam1 ~ factor(center) + age + factor(sex), random= ~1|iid, data=chaidata, varlist=kmat) Error in Y - fitt

Re: [Rd] Strange error message

Brian, Thank you. This explains why it works in Splus: PROTECT is a null macro there, so I wouldn't have caught the miscount. Terry __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Strange error message

This indicates that your PROTECTs and UNPROTECTs are out of balance (by one, looking at the numbers) in the .Call (which I assume is to your own code?). On Tue, 6 Jan 2009, Terry Therneau wrote: I'm testing out some changes to survreg and got the following output, the likes of which I've neve

[Rd] Strange error message

I'm testing out some changes to survreg and got the following output, the likes of which I've never seen before: -- R version 2.7.1 (2008-06-23) Copyright (C) 2008 The R Foundation for Statistical Computing ISBN 3-900051-07-0 R

[Rd] strange error message get from La.svd(X)

Generator Microsoft Word 11 (filtered medium) Hi, I'm the mannova package maintainer. We used La.svd(X, method="dgesvd") in maanova package before. After R-2.3.0, the old La.svd() method was deprecated for option method="dgesvd". I changed maanova code correspondingly, which will call method="d

Re: [Rd] strange error from R CMD check about xaxp

I've also seen this checking randomForest. It looks like the result of memory corruption, so please try with valgrind and/or using gctorture. On Wed, 29 Nov 2006, Liaw, Andy wrote: > Dear R-devel, > > Kurt had alerted me to the problem that the randomForest package that I > maintain has been fa

[Rd] strange error from R CMD check about xaxp

Dear R-devel, Kurt had alerted me to the problem that the randomForest package that I maintain has been failing checks in R-devel. However, I just can't see why or where it's failing. I'd very much appreciate any pointer. The failure occur when running the example code in varImpPlot.Rd: > varI