-
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
GH-38226: [R] Remove R 3.5 from test-r-versions #38230
Conversation
|
@github-actions crossbow submit test-r-versions |
Revision: 2dfeea5 Submitted crossbow builds: ursacomputing/crossbow @ actions-e74b2a9b36
|
### Rationale for this change The test-r-versions job is failing because not all of our dependencies support R 3.5. We follow the tidyverse support policy where possible, which means we only support R 3.6 and above. Thus, we can drop the test for R 3.5. ### What changes are included in this PR? R 3.5 was removed from the test matrix for test-r-versions ### Are these changes tested? Yes ### Are there any user-facing changes? No * Closes: #38226 Authored-by: Dewey Dunnington <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
### Rationale for this change The test-r-versions job is failing because not all of our dependencies support R 3.5. We follow the tidyverse support policy where possible, which means we only support R 3.6 and above. Thus, we can drop the test for R 3.5. ### What changes are included in this PR? R 3.5 was removed from the test matrix for test-r-versions ### Are these changes tested? Yes ### Are there any user-facing changes? No * Closes: apache#38226 Authored-by: Dewey Dunnington <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit ec08625. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 4 possible false positives for unstable benchmarks that are known to sometimes produce them. |
### Rationale for this change The test-r-versions job is failing because not all of our dependencies support R 3.5. We follow the tidyverse support policy where possible, which means we only support R 3.6 and above. Thus, we can drop the test for R 3.5. ### What changes are included in this PR? R 3.5 was removed from the test matrix for test-r-versions ### Are these changes tested? Yes ### Are there any user-facing changes? No * Closes: apache#38226 Authored-by: Dewey Dunnington <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
### Rationale for this change The test-r-versions job is failing because not all of our dependencies support R 3.5. We follow the tidyverse support policy where possible, which means we only support R 3.6 and above. Thus, we can drop the test for R 3.5. ### What changes are included in this PR? R 3.5 was removed from the test matrix for test-r-versions ### Are these changes tested? Yes ### Are there any user-facing changes? No * Closes: apache#38226 Authored-by: Dewey Dunnington <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
### Rationale for this change The test-r-versions job is failing because not all of our dependencies support R 3.5. We follow the tidyverse support policy where possible, which means we only support R 3.6 and above. Thus, we can drop the test for R 3.5. ### What changes are included in this PR? R 3.5 was removed from the test matrix for test-r-versions ### Are these changes tested? Yes ### Are there any user-facing changes? No * Closes: apache#38226 Authored-by: Dewey Dunnington <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
Rationale for this change
The test-r-versions job is failing because not all of our dependencies support R 3.5. We follow the tidyverse support policy where possible, which means we only support R 3.6 and above. Thus, we can drop the test for R 3.5.
What changes are included in this PR?
R 3.5 was removed from the test matrix for test-r-versions
Are these changes tested?
Yes
Are there any user-facing changes?
No