Thanks to Iñaki for the correct diagnosis.
He also pointed out that setting the environment variable
R_C_BOUNDS_CHECK=yes as described in ?options would reproduce the error.
It seems this environment variable is set on CRAN's pre-test environment,
but not on any of the other environments I was te
Inline:
On 2018-07-26 21:11, Brad Eck wrote:
Dear list,
I'm having trouble reproducing errors from CRAN's pretests.
I have a package on CRAN called epanet2toolkit that provides R bindings
to a legacy simulation engine written in C. So far I've released two
versions
to CRAN without trouble. N
I think several of us have had similar issues lately. You might have seen my
posts on reverse dependencies.
It seems there are some sensitivities in the CRAN test setup, though I think
things are improving.
Last week I submitted optimx again. I don't think I changed anything but the
date and so
Hi, a couple of things,:
1) Have you checked the rchk report for possible issues?
https://raw.githubusercontent.com/kalibera/cran-checks/master/rchk/results/epanet2toolkit.out
2) Here there's a call to RENgettimeparam, which passes an empty
character buffer:
https://github.com/bradleyjeck/epane
Dear list,
I'm having trouble reproducing errors from CRAN's pretests.
I have a package on CRAN called epanet2toolkit that provides R bindings
to a legacy simulation engine written in C. So far I've released two
versions
to CRAN without trouble. Now I'm making a third release, principally to
in
