-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[CI][R] Binary package job for R 4.1 on Windows is failed with purrr 1.0.0 #15080
Comments
Purrr already has a patch merged: tidyverse/purrr#1017 We could switch to purr Dev version until it is on cran? |
Thanks for the information!
It's an option. I skipped R 4.1 on Windows job in #15075 . |
purrr will release a fix to cran in early january |
Thanks for the information! |
this now also causes an ERROR on CRAN @nealrichardson |
👍 will keep an eye on it. CRAN hasn't bugged me about it; I'm guessing they know what's up. |
Describe the bug, including details regarding any error messages, version, and platform.
With purrr 0.3.5 (success): https://github.com/ursacomputing/crossbow/actions/runs/3756216656/jobs/6382536442
With purrr 1.0.0 (failed): https://github.com/ursacomputing/crossbow/actions/runs/3756216656/jobs/6406276507
Note that the above two jobs are the same revision. The former was ran at 2022-12-22. The latter was re-ran at 2022-12-24.
https://cran.r-project.org/package=purrr says purrr 1.0.0 was published at 2022-12-20:
Note that R 4.2 on Windows job doesn't have this problem.
Component(s)
Continuous Integration, Packaging, R
The text was updated successfully, but these errors were encountered: