Closed sbfnk closed 1 month ago
Related: https://github.com/stan-dev/rstan/issues/1122 https://github.com/stan-dev/rstan/pull/1124#issuecomment-2075003911
I believe that these are most likely out-of-memory issues in the compiler (Terminated
is distinct from an error and usually means the OS killed the process). If that's the case, it is unclear what we can do about it.
Seems to have been a transient issue that has resolved itself.
Summary:
Quite a few packages that depend on rstan currently error on some platforms during compilation on CRAN.
Description:
A few examples (the first ones when going through alphabetically) are
https://cran.r-project.org/web/checks/check_results_baggr.html https://cran.r-project.org/web/checks/check_results_bakR.html https://cran.r-project.org/web/checks/check_results_baldur.html
The final line in the log is
No error is reported, and we have been unable to reproduce this locally using the same r-patched revision for EpiNow2. Perhaps a memory issue?
If this remains it is likely to cause issues for CRAN submission of packages that depend on
rstan