-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRAN failures #21
Comments
I can reproduce via |
That code is now in this branch. |
I am currently travelling, but I will see if I can solve the underlying problem on Monday. |
Thanks for the feedback. We can wait a few days. We could also upload the fix now, and then have no time pressure to work on the underlying issue. |
The CRAN checks now show test failures on Debian as well. I just updated my local R-devel on Debian bullseye and could reproduce the failure locally, so I can start tracking it down. |
Good catch! I just updated r-devel to SVN r80309 as of today here, and that makes 0.3.17 fail for me too (and renders my local 0.3.17.1 invalid as 'test only on Debian' no longer works, it really is an R-devel issue. So maybe wholesale suppression of moveDLL tests unless opted in (locally, by you or me; or unless R version <= 4.0.5) is safest unless you actually find a fix ... |
I presume the mail below was triggered by you. Hint: change Maintainer: to your email to get the reply. I also strongly suggest to not use release versions. My draft is 0.3.17.1, not 0.3.18.
|
@jranke :-/ "No rest for the wicked" as they say. Version 0.3.18 still fails on M1mac (follow the link to see it is 0.3.18) and failed on Slowlaris: https://cloud.r-project.org/web/checks/check_results_inline.html Should we play it a little more defensively and ... just turn those |
KH emailed
@jranke I may need your help here as the issues, following the link above appear to end in the tests for
moveDLL
applied toquadfun
:I'll start by trying to reproduce on RHub.
The text was updated successfully, but these errors were encountered: