I think (but I am not sure) that I narrowed down the issue to a stochastic
process that has no seed defined. Unfortunately it's not my package so I have
to do mostly guesswork on this regard.
What has surprised me though, is that I managed to get exact same results on
three different platforms (
it probably makes sense to more directly indicate what package is causing
problems (e.g., sharing the location of a public repository of the source) and
the nature of the error (cut-and-paste the check output here?). Likely this
will lead both to insight into the problem being flagged by the bui
On 31 January 2020 at 09:11, Borini, Stefano wrote:
| Thanks. What is the recommended strategy in this case? Keep submitting and
patching until it passes?
Standard debugging, and (as Uwe already said) win-builder for that OS, rhub
for others, and asking here, ... Imperfect, but doable.
It wou
Thanks. What is the recommended strategy in this case? Keep submitting and
patching until it passes?
On 30/01/2020, 22:48, "Dirk Eddelbuettel" wrote:
On 30 January 2020 at 21:40, Borini, Stefano wrote:
| I am currently trying to submit a package to CRAN, and I see no problems
in run
