Skip to content
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

Make R 4.1 on Windows a new "special" in examples/check-full.yaml #564

Closed
jennybc opened this issue May 18, 2022 · 1 comment
Closed

Make R 4.1 on Windows a new "special" in examples/check-full.yaml #564

jennybc opened this issue May 18, 2022 · 1 comment

Comments

@jennybc
Copy link
Member

jennybc commented May 18, 2022

Capturing a recent slack discussion.

We should add R 4.1 + windows-latest to the standard matrix in examples/check-full.yaml.

The argument is similar to that for keeping R 3.6 + windows-latest around: making sure to test with a previous toolchain, Rtools35.

With the release of R 4.2, now it's important to test on R 4.1 + windows-latest to retain coverage of RTools40 and a native encoding that's not UTF-8.

For practical reasons, this means we will probably drop R 3.6 + windows-latest from our standard matrix, since we're already flirting with various limits. Specific packages could choose to retain R 3.6 + windows-latest in the matrix, if it has proven to be helpful in recent memory.

We support R release + 4 previous versions on Windows, macOS, and Linux. But we don't test that complete matrix, rather we test one complete row and one complete column in the table below PLUS we add any special high-risk combinations (e.g. R 4.1 + windows-latest).

           lin win mac
devel      +    -   -
release    +    +   +
oldrel-1   +    -   -
oldrel-2   +    -   -
oldrel-3   +    -   -
oldrel-4   +    -   -
@github-actions
Copy link

github-actions bot commented Nov 4, 2022

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant