-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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-41402: [CI][R] Update our backwards compatibility CI any other R 4.4 cleanups #41403
Conversation
|
@github-actions crossbow submit test-r-arrow-backwards-compatibility |
Revision: 6b5dda3 Submitted crossbow builds: ursacomputing/crossbow @ actions-3ae27aae8b
|
@github-actions crossbow submit -g r |
Revision: f31f859 Submitted crossbow builds: ursacomputing/crossbow @ actions-802b06fdc8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks for updating everything! The ci errors are mostly #41359 and likely unrelated (valgrind/ubsan). Not sure whats going on with the offline install but that's also failing on main.
@@ -35,7 +35,7 @@ ENV LANG=C.UTF-8 | |||
# Build R | |||
# [1] https://www.digitalocean.com/community/tutorials/how-to-install-r-on-ubuntu-18-04 | |||
# [2] https://linuxize.com/post/how-to-install-r-on-ubuntu-18-04/#installing-r-packages-from-cran | |||
ARG r=3.6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oO :D
@@ -140,7 +140,7 @@ register_bindings_type_cast <- function() { | |||
fix.empty.names = TRUE, | |||
stringsAsFactors = FALSE) { | |||
# we need a specific value of stringsAsFactors because the default was | |||
# TRUE in R <= 3.6 | |||
# TRUE in R <= 3.6 and folks might still be cargoculting to stay in the past. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😁
@github-actions crossbow submit test-r-offline-maximal |
Revision: f565fe6 Submitted crossbow builds: ursacomputing/crossbow @ actions-dbb88ab3ac
|
@github-actions crossbow submit test-r-versions |
Revision: f565fe6 Submitted crossbow builds: ursacomputing/crossbow @ actions-eb08160d5b
|
@github-actions crossbow submit test-r-offline-maximal |
Revision: 403c579 Submitted crossbow builds: ursacomputing/crossbow @ actions-4bdedd0dc6
|
I fixed the maximal offline build, it was checking for docs and we were purposefully not biulding them. This looks to be a slight change in behavior of 4.4.0 where no docs at all and then |
@github-actions crossbow submit test-r-linux-valgrind |
Revision: fcf9e74 Submitted crossbow builds: ursacomputing/crossbow @ actions-944b9b9e08
|
The valgrind cleanup I made probably will not fix the valgrind build (If I'm reading the output correctly, there's still a possible leak). But it will get rid of the silly failures where https://stat.ethz.ch/pipermail/r-devel/2021-April/080683.html So is an improvement (in that the failures are fewer), but might not be enough to have that be green. |
Ooops, also caught that using the old rhub devel images are stuck in December:
I'll bump those to be the new "containers" approach: https://r-hub.github.io/containers/ |
@github-actions crossbow submit test-fedora-r-clang-sanitizer test-r-rhub-debian-gcc-devel-lto-latest |
Yeah, I'll bump to 4.0 in the DESCRIPTION. I get we could have 3.6 there but I would rather pull out our random backports than have a lower (unsupported) version there. |
@github-actions crossbow submit r-binary-packages test-r-linux-valgrind |
Revision: 8d91cab Submitted crossbow builds: ursacomputing/crossbow @ actions-bb446802ac
|
@github-actions crossbow submit r-binary-packages |
Revision: 67941ba Submitted crossbow builds: ursacomputing/crossbow @ actions-437d88c30f
|
@github-actions crossbow submit r-binary-packages @jonkeane I added the fix for the upload job just so we can potentially merge this if we want to get it into 16.1. Hope that's ok! |
I'm happy for it to merge now. There are a few follow ons but I think those would be better separately! Thanks for the fix for the binaries |
Revision: 8cad637 Submitted crossbow builds: ursacomputing/crossbow @ actions-c2f5ac8f88
|
@jonkeane it looks like openssl is still not being picked up correctly so we probably need to look at that again. I think this is also caused by the change to the gh macos runners, I think I manually installed the cran openssl there... I will open an issue for a follow up. |
….4 cleanups (#41403) ### Rationale for this change Keep up with the state of the world, ensure we are maintaining backwards compatibility. Resolves #41402 ### What changes are included in this PR? * Bump to 4.4 as the release * Remove old 3.6 jobs now that we no longer support that; clean up code where we hardcode things fro 3.6 and below * Move many of our CI jobs to [rhub's new containers](https://github.com/r-hub/containers). We were accidentally running stale R devel (from December 2023) because the other rhub images stopped being updated. (One exception to be done as a follow on: #41416) * Resolve a number of extended test failures With this PR R extended tests should be all green with the exceptions of: * Two sanitizer jobs (test-fedora-r-clang-sanitizer, test-ubuntu-r-sanitizer) — which are being investigated / fixed in #41421 * Valgrind — I'm running one last run with a new suppression file. * Binary jobs — these work but fail at upload, see #41403 (comment) * Windows R Release — failing on main, #41398 ### Are these changes tested? By definition. ### Are there any user-facing changes? No. * GitHub Issue: #41402 Lead-authored-by: Jonathan Keane <jkeane@gmail.com> Co-authored-by: Jacob Wujciak-Jens <jacob@wujciak.de> Signed-off-by: Jonathan Keane <jkeane@gmail.com>
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 6eb0b37. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
…er R 4.4 cleanups (apache#41403) ### Rationale for this change Keep up with the state of the world, ensure we are maintaining backwards compatibility. Resolves apache#41402 ### What changes are included in this PR? * Bump to 4.4 as the release * Remove old 3.6 jobs now that we no longer support that; clean up code where we hardcode things fro 3.6 and below * Move many of our CI jobs to [rhub's new containers](https://github.com/r-hub/containers). We were accidentally running stale R devel (from December 2023) because the other rhub images stopped being updated. (One exception to be done as a follow on: apache#41416) * Resolve a number of extended test failures With this PR R extended tests should be all green with the exceptions of: * Two sanitizer jobs (test-fedora-r-clang-sanitizer, test-ubuntu-r-sanitizer) — which are being investigated / fixed in apache#41421 * Valgrind — I'm running one last run with a new suppression file. * Binary jobs — these work but fail at upload, see apache#41403 (comment) * Windows R Release — failing on main, apache#41398 ### Are these changes tested? By definition. ### Are there any user-facing changes? No. * GitHub Issue: apache#41402 Lead-authored-by: Jonathan Keane <jkeane@gmail.com> Co-authored-by: Jacob Wujciak-Jens <jacob@wujciak.de> Signed-off-by: Jonathan Keane <jkeane@gmail.com>
…er R 4.4 cleanups (apache#41403) ### Rationale for this change Keep up with the state of the world, ensure we are maintaining backwards compatibility. Resolves apache#41402 ### What changes are included in this PR? * Bump to 4.4 as the release * Remove old 3.6 jobs now that we no longer support that; clean up code where we hardcode things fro 3.6 and below * Move many of our CI jobs to [rhub's new containers](https://github.com/r-hub/containers). We were accidentally running stale R devel (from December 2023) because the other rhub images stopped being updated. (One exception to be done as a follow on: apache#41416) * Resolve a number of extended test failures With this PR R extended tests should be all green with the exceptions of: * Two sanitizer jobs (test-fedora-r-clang-sanitizer, test-ubuntu-r-sanitizer) — which are being investigated / fixed in apache#41421 * Valgrind — I'm running one last run with a new suppression file. * Binary jobs — these work but fail at upload, see apache#41403 (comment) * Windows R Release — failing on main, apache#41398 ### Are these changes tested? By definition. ### Are there any user-facing changes? No. * GitHub Issue: apache#41402 Lead-authored-by: Jonathan Keane <jkeane@gmail.com> Co-authored-by: Jacob Wujciak-Jens <jacob@wujciak.de> Signed-off-by: Jonathan Keane <jkeane@gmail.com>
Rationale for this change
Keep up with the state of the world, ensure we are maintaining backwards compatibility.
Resolves #41402
What changes are included in this PR?
rhub/clang-asan
image #41416)With this PR R extended tests should be all green with the exceptions of:
Are these changes tested?
By definition.
Are there any user-facing changes?
No.