-
Notifications
You must be signed in to change notification settings - Fork 47
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
Possibly unintentional breakage on 32 bit Windows and R 3.6 #501
Comments
@jeroen has confirmed this affects R 4.0 and 4.1 with 32 bit Windows as well (we don't explicitly run those checks) At 4.2 R dropped support for 32 bit Windows, which is possibly why CRAN probably didn't detect this |
It looks like the So if I suppose if we would want to fix this, we could backport this hack that avoids the call to |
I was able to fix this on my local 32-bit Windows VM, but it's still failing to install via GH actions. @jeroen any chance you could help me debug it? This job fails with the rather cryptic message:
|
I'm not sure why the CI fails. But R-3.6 included a very old version of bash and make, that have problems with some paths and long commands. Honestly I would not bother too much. Nobody uses R-3.6 anymore so you can just bump the CI version to R-4.0 as you already do in order to make sure that 32-bit works. I confirmed manually that R-3.6 does in fact work, just the CI does not. |
Thanks for digging into this. Do you suggest adding |
Just leave as-is, but stop actively testing R-3.6-Windows it in CI. But we don't want to prevent people from installing stringi on R 3.6, especially on Linux, where some people do run very old versions of R. |
Makes sense. Thanks again! |
I see there is a new stringi release and I happened to just note that our R 3.6 Windows build is failing due to an inability to build stringi from source in the 32 bit checks:
https://github.com/tidyverse/dplyr/actions/runs/6896097548/job/18761489770?pr=6967#step:5:4120
I think the relevant lines are:
I didn't see a note in the NEWS about this, so just wanted to check if this was intentional or not
(In the tidyverse we tend to try and support 5 minor versions of R, so that is why we still have R 3.6 checks running)
The text was updated successfully, but these errors were encountered: