On 9/17/19 6:17 PM, Cristiane Hayumi Taniguti wrote:
Hello, thanks for all the answers.
I did the new tests with all suggestions.
I included the Rprintf in my script, however it did not show any NaN when
running with my examples (the same that CRAN check pointed the error)
The approach of add
Hello, thanks for all the answers.
I did the new tests with all suggestions.
I included the Rprintf in my script, however it did not show any NaN when
running with my examples (the same that CRAN check pointed the error)
The check in r-hub Debian Linux, R-devel, GCC ASAN/UBSAN
(linux-x86_64-rock
On Fri, 13 Sep 2019 at 16:16, Cristiane Hayumi Taniguti
wrote:
>
> ...twopts_f2.cpp:101:7: runtime error: nan is
> outside the range of representable values of type 'int'
> onemap.Rcheck/onemap-Ex.Rout:twopts_f2.cpp:101:26: runtime error: nan is
> outside the range of repre
As first step of being able to reproduce the error, have a look at
R-Hub (https://blog.r-hub.io/2019/03/26/why-care/). It'll allow you
to use their servers to test your package on many different
configurations. It helped me several times. You can launch it all
from you local R prompt, e.g.
> rhu
On 13/09/2019 10:15 a.m., Cristiane Hayumi Taniguti wrote:
I'm having difficulties updating my package onemap: When I run standard
checks as --as-cran in linux, winbuilder and using docker images everything
is fine, but 'CRAN-submissions' reports this problem in my c++ code:
onemap.Rcheck/onemap
I'm having difficulties updating my package onemap: When I run standard
checks as --as-cran in linux, winbuilder and using docker images everything
is fine, but 'CRAN-submissions' reports this problem in my c++ code:
onemap.Rcheck/onemap-Ex.Rout:
.../usr/local/bin/../include/c++/v1/mem
