I'm updating the rgl package, and have come across the following problem.
Some packages that depend on rgl and do careful testing are detecting
inconsequential changes. A typical case is the nat package, which has
extensive testing, some of which comes down to checking results from rgl
functi
An all.equal method? This might not work with 3rd edition though
(untested), and I'm not sure what method registration requirements
would exist for the user.
Best,
B.
On Friday, April 16, 2021, 6:09:24 AM EDT, Duncan Murdoch
wrote:
I'm updating the rgl package, and have come across the
My 2c is that if a package has actually tested something like that
(say, the ordering of a list's elements), then it is 100% likely that
a script out there depends on that behaviour too. In other words, the
change is not inconsequential. R users are in debt to package
developers but I think it be
On 16/04/2021 7:40 a.m., brodie gaslam wrote:
An all.equal method? This might not work with 3rd edition though
(untested), and I'm not sure what method registration requirements
would exist for the user.
It already has one, but it isn't used by testthat 3.
Duncan Murdoch
On 16/04/2021 7:54 a.m., Hugh Parsonage wrote:
My 2c is that if a package has actually tested something like that
(say, the ordering of a list's elements), then it is 100% likely that
a script out there depends on that behaviour too.
I suspect this test is not intentional, and it really wouldn
Hello,
We publish in CRAN our package rTLS [1]. The package passed the test
without problems. However, at some point, additional testing suggests that
it has issues with 'gcc-ASAN' [2]. For me this error is not informative,
and thus, I do not have an idea how to start. I have been looking for
guid
> On 16 Apr 2021, at 14:06, Duncan Murdoch wrote:
>
> On 16/04/2021 7:54 a.m., Hugh Parsonage wrote:
>> My 2c is that if a package has actually tested something like that
>> (say, the ordering of a list's elements), then it is 100% likely that
>> a script out there depends on that behaviour too
An offline message said
"Oh, you mean you're asking for an actual object-oriented language that
hides the internal representations of objects from users of a package.
Unfortunately for all of us, that isn't R."
Actually, I don't think that's what I want. We already have lots of
languages l
Another approach is to change the responsibility.
My feeling is that tests in the TESTING package should be modifiable by the
maintainer of
the TESTED package, with both packages suspended if the two maintainers cannot
agree. We
need to be able to move forward when legacy behaviour is outdated o
On 16/04/2021 9:49 a.m., J C Nash wrote:
Another approach is to change the responsibility.
My feeling is that tests in the TESTING package should be modifiable by the
maintainer of
the TESTED package, with both packages suspended if the two maintainers cannot
agree. We
need to be able to move
I'm generally in accord with Duncan on this. There are inevitably situations
where general
rules don't apply. Our challenge is to find practical ways to keep the overall
workload of
all participants in the process to a minimum.
JN
On 2021-04-16 10:18 a.m., Duncan Murdoch wrote:
> On 16/04/2021
One of the basic principles of testing is "test interface, not
implementation." Tests that violate this principle become "change detector
tests" instead of "correctness tests" and essentially prevent any
improvements to the code. In C++ objects have "public" and "private"
methods, and the testing
Hello,
We publish in CRAN our package rTLS [1]. The package passed the test
without problems. However, at some point, additional testing suggests that
it has issues with 'gcc-ASAN' [2]. For me this error is not informative,
and thus, I do not have an idea how to start. I have been looking for
guid
>From https://www.stats.ox.ac.uk/pub/bdr/memtests/gcc-ASAN/rTLS/00check.log,
you can see errors of the form:
==3566104==ERROR: AddressSanitizer: stack-use-after-scope on address
0x7fffc2651f80 at pc 0x7f7ba5b635de bp 0x7fffc2651eb0 sp
0x7fffc2651ea0
< ... >
The slides here explain what that means
Hi all,
I am trying to submit an update to my package
(https://cran.r-project.org/package=Signac) to CRAN, but it is
currently failing to install on the Windows server. I see the
following installation error: "namespace 'rtracklayer' 1.48.0 is being
loaded, but >= 1.51.5 is required."
The current
On 16 April 2021 at 10:27, Kevin Ushey wrote:
| You can also try to verify locally using e.g. Docker; the rocker
| images here are immensely helpful:
|
| https://github.com/rocker-org/r-devel-san
Thanks but that container image may be stale at times. The daily rebuilds by
Kevin's colleague Wins
When a script in tests/ is being run by R CMD check and friends, can we know
what package it is currently being part of? I want to access some package
files via system.file(..., package=pkg) which works just fine, but it feels
redundant to assign the package name to the pkg variable.
Case in
Hello,
Thanks for your response Kevin. It works using 'inplace_trans()', but it
takes a long time to solve.
I will try to reproduce the error using Dirk's suggestion.
Your guides are appreciated.
AG.
El vie, 16 abr 2021 a las 17:00, Dirk Eddelbuettel ()
escribió:
>
> On 16 April 2021 at 10:27
18 matches
Mail list logo
