I don't think it is specific for testthat. R CMD check sets R_TESTS when it
runs the tests, so the separate R process it starts can have some special
startup options.
The problem happens if you start another R process from your R test, and
then R_TESTS confuses this process. (I am not sure how exa
Before submitting a package-update, I visit the check-results-page, as
requested by CRAN. For my sjstats-package, there is an error on
r-patched-solaris for package version 0.8.0:
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/sjstats-00check.html
it says:
Waiting for profiling
On 06.02.2017 12:09, Daniel Lüdecke wrote:
Before submitting a package-update, I visit the check-results-page, as
requested by CRAN. For my sjstats-package, there is an error on
r-patched-solaris for package version 0.8.0:
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/sjstats-0
> Well, this is on Solaris, not Linux, most likely it is an issue on your
Yes, I recognized this just after sending the mail I'm just curious why
this does only happen on Solaris, and not other machines. According to
the traceback, this error seems to occur when computing CI for glm:
Tracebac
