Thanks for the feedback Dirk. I sent my follow-up before I saw it.
Looking at the source code, it appears that there is no options() call to turn this on.
Nor does "R --help" reveal a command line option.
How then does a user turn this on outside of the R CMD check envirionment, so as to
On 13/01/2020 11:02 a.m., Therneau, Terry M., Ph.D. via R-devel wrote:
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
From R NEWS (changes in 3.6.0)
Experimentally, setting environment variable _R_CHECK_LENGTH_1_LOGIC2_
will lead to warnings (or errors if the variable is set to a ‘true’
value) when && or || encounter and use arguments of length more than one.
On 2020-01-13 11:46 a.m., Therneau, Terry M.,
> Ben Bolker
> on Mon, 13 Jan 2020 11:49:09 -0500 writes:
> From R NEWS (changes in 3.6.0)
> Experimentally, setting environment variable _R_CHECK_LENGTH_1_LOGIC2_
> will lead to warnings (or errors if the variable is set to a ‘true’
> value) when && or || encounter
I've been fighting a CMD check error for coxme this morning. I thought I had
it fixed,
but instead I had forgotton --as-cran on my last test run. So the version just
submitted
to CRAN has warning messages in the log.
I think it is an issue with CRAN. I've sent a message to R-devel asking
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,
On 13 January 2020 at 10:02, Therneau, Terry M., Ph.D. via R-devel wrote:
| Where can I find out (and replicate) what options as-cran turns on?
See the file src/library/tools/R/check.R in the R sources, and grep for
as_cran which is the internal variable controlled by the --as-cran option
Those of us stuck on Windows but who attempt to develop properly are
wounded to the quick, sir!
:)
Avi
On Mon, Jan 13, 2020 at 12:24 PM Martin Maechler
wrote:
> > Ben Bolker
> > on Mon, 13 Jan 2020 11:49:09 -0500 writes:
>
> > From R NEWS (changes in 3.6.0)
> >
Thank you to all who replied with helpful suggestions. I had to run off to
meetings and
talks for a bit so am now processing it all.
1. It turns out that the issue was not with coxme, but with bsdmatrix, a
package that
coxme calls. It just happens to have a function ismat() with the same
On 13 January 2020 at 14:51, Therneau, Terry M., Ph.D. wrote:
| 3. Dirk gave good input about the flags in R CMD check and how to find them.
One more
| line in the "Writing R Extensions" manual would have been helpful, namely
that many of the
| options are NOT available in the options()
Good catch, Ivan! Fixing that seems to have done the trick. Thanks!
The question now is why checkpoint hasn't crashed and burned prior to this, but
I'll leave that for another day
-Original Message-
From: Ivan Krylov
Sent: Friday, 10 January 2020 8:18 PM
To: Hong Ooi via
El lun., 13 ene. 2020 11:45, Hong Ooi via R-package-devel <
r-package-devel@r-project.org> escribió:
> Good catch, Ivan! Fixing that seems to have done the trick. Thanks!
>
> The question now is why checkpoint hasn't crashed and burned prior to
> this, but I'll leave that for another day
Hi Lori,
I have already fixed the issues on the master and devel versions.
thanks for your assistance.
Juan Cruz Rodriguez
El mar., 7 ene. 2020 a las 13:37, Shepherd, Lori (<
lori.sheph...@roswellpark.org>) escribió:
> Yes it should be. The automatic build failure messages and when we reach
>
13 matches
Mail list logo
