-
Notifications
You must be signed in to change notification settings - Fork 42
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
critical failure -- need CRAN release in a week or so #2073
Comments
Hm. I am not 100% sure what the error is. I see this "OMP" problem, which is not something I understand. Below that, I see a problem with a But first I'll try build-test the CRAN source. |
FYI |
Given comments from a CRAN member, and after discussion with @richardsc, I have decided to comment-out all We have only 37 cases.
|
Actually, I am going to remove the lines, instead of commenting them out. That ought to be clearer (which is relevant given a comment from a CRAN member about obfuscation). We can rely on a good git commit to tell us about what has changed. |
After some discussion with CR, my present plan is to move the |
I've moved the tests involving |
Below is a new error on CRAN package check. The error appears on several test machines. (I thank BR for pointing this out.)
The text was updated successfully, but these errors were encountered: