Thank you Georgi and Uwe! I've made doubly sure that "examples_and_tests"
isn't in my tarball and I've uploaded again to CRAN.
yours
Kassel
On Fri, 7 Jun 2019 at 17:07, Uwe Ligges
wrote:
> Or you have been there at the wrong time when we enabled a new check
> that was not able to correctly
On Fri, Jun 7, 2019 at 11:09 AM Dirk Eddelbuettel wrote:
>
> On 7 June 2019 at 10:13, Tim Keitt wrote:
> | I bumped a package to CXX14/17 and it failed on Travis/Appveyor while
> | checking fine locally. I assume I need to request different compilers or
>
> Correct.
>
> Working with a seriously
On 07/06/2019 1:53 p.m., William Dunlap wrote:
I've attached a package, ppp_0.1.tar.gz, which probably will not get
through to R-help, that illustrates this.
It contains one function which, by default, triggers a
condition-length>1 issue:
f <- function(x = 1:3)
{
if (x > 1) {
A simplified version without a package:
Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_"="abort,verbose")
tryCatch(1:3 || 1, error = identity)
Running this aborts the session since it calls R_Suicide without first
signaling a condition to try any available handlers. Should be easy to
change, but I don't
I've put my tiny package back up, but it likely is doing same
thing as Bill Dunlap's. I took it off as a cleanup when I thought
the issue resolved.
http://web.ncf.ca/fh448/jfiles/fchk_2019-6.5.tar.gz
Seems I've disturbed the ant's nest.
JN
On 2019-06-07 1:53 p.m., William Dunlap wrote:
>
I've attached a package, ppp_0.1.tar.gz, which probably will not get
through to R-help, that illustrates this.
It contains one function which, by default, triggers a condition-length>1
issue:
f <- function(x = 1:3)
{
if (x > 1) {
x <- -x
}
stop("this function
Duncan and others, see one of Serguei comments above. Specifically,
`R CMD check --as-cran` will set
_R_CHECK_LENGTH_1_LOGIC2_="package:_R_CHECK_PACKAGE_NAME_,abort,verbose"
which will (i) check those coding mistakes only in the package that is
checked but not any of its dependencies, (ii) it
On 07/06/2019 12:32 p.m., William Dunlap wrote:
The length-condition-not-equal-to-one checks will cause R to shutdown
even if the code in a tryCatch().
That's strange. I'm unable to reproduce it with my tries, and John's
package is no longer online. Do you have an example I could look at?
The length-condition-not-equal-to-one checks will cause R to shutdown even
if the code in a tryCatch().
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Fri, Jun 7, 2019 at 7:47 AM Duncan Murdoch
wrote:
> On 07/06/2019 9:46 a.m., J C Nash wrote:
> > Should try() not stop those checks from
On 7 June 2019 at 10:13, Tim Keitt wrote:
| I bumped a package to CXX14/17 and it failed on Travis/Appveyor while
| checking fine locally. I assume I need to request different compilers or
Correct.
Working with a seriously outdated base layer of Ubuntu is a key bug^Hfeature
of Travis.
On 07/06/2019 16:47, Duncan Murdoch wrote:
On 07/06/2019 9:46 a.m., J C Nash wrote:
Should try() not stop those checks from forcing an error?
try(stop("msg")) will print the error message, but won't stop
execution. Presumably the printed message is what is causing you
problems. If you
I bumped a package to CXX14/17 and it failed on Travis/Appveyor while
checking fine locally. I assume I need to request different compilers or
something like that. Anyone have a quick recipe for that?
THK
[[alternative HTML version deleted]]
On 07/06/2019 9:46 a.m., J C Nash wrote:
Should try() not stop those checks from forcing an error?
try(stop("msg")) will print the error message, but won't stop
execution. Presumably the printed message is what is causing you
problems. If you want to suppress that, use
try(stop("msg"),
Serguei picked up the glitch and Jeff sorted out the || vs | once any()
was used.
The test that caused the issue was not the one I was looking for,
but another case. However, I'd overlooked the possibility that
there could be different lengths, so || complained (as it should,
but didn't in
On 07/06/2019 16:05, Jeff Newmiller wrote:
any(is.infinite(fval)) || any(is.na(fval))
a little typo here: it should be '|', not '||', right ?
Since `any` collapses the vectors to length 1 either will work, but I would
prefer `||`.
You are right, I missed the second 'any()' at the first
>> any(is.infinite(fval)) || any(is.na(fval))
>
>a little typo here: it should be '|', not '||', right ?
Since `any` collapses the vectors to length 1 either will work, but I would
prefer `||`.
On June 7, 2019 6:51:29 AM PDT, Serguei Sokol wrote:
>On 07/06/2019 15:31, Sebastian Meyer wrote:
>>
On 07/06/2019 15:31, Sebastian Meyer wrote:
The failure stated in the R CMD check failure report is:
--- failure: length > 1 in coercion to logical ---
This comes from --as-cran performing useful extra checks via setting the
environment variable _R_CHECK_LENGTH_1_LOGIC2_, which means:
On 07/06/2019 14:53, J C Nash wrote:
Sorry reply not quicker. For some reason I'm not getting anything in the thread
I started!
I found the responses in the archives. Perhaps cc: nas...@uottawa.ca please.
I have prepared a tiny (2.8K) package at
Should try() not stop those checks from forcing an error?
I recognize that this is the failure -- it is indeed the check I'm trying to
catch -- but I don't want tests of such checks to fail my package.
JN
On 2019-06-07 9:31 a.m., Sebastian Meyer wrote:
> The failure stated in the R CMD check
The failure stated in the R CMD check failure report is:
> --- failure: length > 1 in coercion to logical ---
This comes from --as-cran performing useful extra checks via setting the
environment variable _R_CHECK_LENGTH_1_LOGIC2_, which means:
> check if either argument of the binary operators
Sorry reply not quicker. For some reason I'm not getting anything in the thread
I started!
I found the responses in the archives. Perhaps cc: nas...@uottawa.ca please.
I have prepared a tiny (2.8K) package at
http://web.ncf.ca/nashjc/jfiles/fchk_2019-6.5.tar.gz
R CMD check --> OK
R CMD check
Dear Duncan,
Thank you very much!
>
> For data, the sysdata.rda file is the easiest solution. It's for data
> that is used by the functions in the package, not user-visible. Just
> put x into that file in the package/R directory to make use of it.
>
> You don't need a two-pass solution. As
Right, what problem are you talking about? Can you tell us which check
it is and what it actually complained about.
There is no check that looks at the sizes of x and y in exypressions
such as
(x - y)^2.
as far as I know.
Best,
Uwe
On 07.06.2019 10:33, Berry Boessenkool wrote:
Not entirely
Or you have been there at the wrong time when we enabled a new check
that was not able to correctly deal with check directories produced
under bi-arch check siutuations. This is fixed for wionbuilder and wil
be fixed in the R sources soon,
Uwe
On 07.06.2019 09:31, Georgi Boshnakov wrote:
It looks like you get the note when you run the check on the package directory,
rather than on the tarball of the package. Undoubtedly, you submitted the
tarball towinbuilder. develops::check also first builds the package and then
does the flecks on the tarball.
If unwanted files do creep into
Hi All,
This is my first time submitting a package to CRAN, and posting here. I
hope I get everything right.
Checks ran by CRAN for Windows systems generated a note that I don't know
where to start to solve:
* checking for non-standard things in the check directory ... NOTE
Found the following
26 matches
Mail list logo
