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

GH-41402: [CI][R] Update our backwards compatibility CI any other R 4.4 cleanups #41403

Merged
merged 12 commits into from
Apr 29, 2024

Conversation

jonkeane
Copy link
Member

@jonkeane jonkeane commented Apr 26, 2024

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. 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: [R][CI] Use the new rhub/clang-asan image #41416)
  • Resolve a number of extended test failures

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.

Copy link

⚠️ GitHub issue #41402 has been automatically assigned in GitHub to PR creator.

@github-actions github-actions bot added the awaiting committer review Awaiting committer review label Apr 26, 2024
@jonkeane
Copy link
Member Author

@github-actions crossbow submit test-r-arrow-backwards-compatibility

Copy link

Revision: 6b5dda3

Submitted crossbow builds: ursacomputing/crossbow @ actions-3ae27aae8b

Task Status
test-r-arrow-backwards-compatibility GitHub Actions

@kou kou changed the title GH-41402: [CI] [R] Update our backwards compatibility CI any other R 4.4 cleanups GH-41402: [CI][R] Update our backwards compatibility CI any other R 4.4 cleanups Apr 26, 2024
@jonkeane
Copy link
Member Author

@github-actions crossbow submit -g r

Copy link

Revision: f31f859

Submitted crossbow builds: ursacomputing/crossbow @ actions-802b06fdc8

Task Status
r-binary-packages GitHub Actions
test-fedora-r-clang-sanitizer GitHub Actions
test-r-arrow-backwards-compatibility GitHub Actions
test-r-depsource-bundled Azure
test-r-depsource-system GitHub Actions
test-r-dev-duckdb GitHub Actions
test-r-devdocs GitHub Actions
test-r-gcc-11 GitHub Actions
test-r-gcc-12 GitHub Actions
test-r-install-local GitHub Actions
test-r-install-local-minsizerel GitHub Actions
test-r-linux-as-cran GitHub Actions
test-r-linux-rchk GitHub Actions
test-r-linux-valgrind GitHub Actions
test-r-minimal-build Azure
test-r-offline-maximal GitHub Actions
test-r-offline-minimal Azure
test-r-rhub-debian-gcc-devel-lto-latest Azure
test-r-rhub-debian-gcc-release-custom-ccache Azure
test-r-rhub-ubuntu-gcc-release-latest Azure
test-r-rocker-r-ver-latest Azure
test-r-rstudio-r-base-4.1-opensuse153 Azure
test-r-rstudio-r-base-4.2-centos7-devtoolset-8 Azure
test-r-rstudio-r-base-4.2-focal Azure
test-r-ubuntu-22.04 GitHub Actions
test-r-versions GitHub Actions
test-ubuntu-r-sanitizer GitHub Actions

Copy link
Member

@assignUser assignUser left a 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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oO :D

dev/tasks/r/github.linux.versions.yml Show resolved Hide resolved
@@ -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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😁

@github-actions github-actions bot added awaiting changes Awaiting changes and removed awaiting committer review Awaiting committer review labels Apr 27, 2024
@jonkeane
Copy link
Member Author

@github-actions crossbow submit test-r-offline-maximal

@github-actions github-actions bot added awaiting change review Awaiting change review and removed awaiting changes Awaiting changes labels Apr 27, 2024
Copy link

Revision: f565fe6

Submitted crossbow builds: ursacomputing/crossbow @ actions-dbb88ab3ac

Task Status
test-r-offline-maximal GitHub Actions

@jonkeane
Copy link
Member Author

@github-actions crossbow submit test-r-versions

Copy link

Revision: f565fe6

Submitted crossbow builds: ursacomputing/crossbow @ actions-eb08160d5b

Task Status
test-r-versions GitHub Actions

@jonkeane
Copy link
Member Author

@github-actions crossbow submit test-r-offline-maximal

Copy link

Revision: 403c579

Submitted crossbow builds: ursacomputing/crossbow @ actions-4bdedd0dc6

Task Status
test-r-offline-maximal GitHub Actions

@jonkeane
Copy link
Member Author

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 testInstalledPackage fails. We could look into this separately and report upstream, but it's also pretty niche.

@jonkeane
Copy link
Member Author

@github-actions crossbow submit test-r-linux-valgrind

Copy link

Revision: fcf9e74

Submitted crossbow builds: ursacomputing/crossbow @ actions-944b9b9e08

Task Status
test-r-linux-valgrind GitHub Actions

@jonkeane
Copy link
Member Author

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 NAs are sometimes transformed into NaNs

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.

@jonkeane
Copy link
Member Author

Ooops, also caught that using the old rhub devel images are stuck in December:

* using R Under development (unstable) (2023-12-26 r85738)

I'll bump those to be the new "containers" approach: https://r-hub.github.io/containers/

@jonkeane
Copy link
Member Author

@github-actions crossbow submit test-fedora-r-clang-sanitizer test-r-rhub-debian-gcc-devel-lto-latest

@github-actions github-actions bot added awaiting change review Awaiting change review awaiting changes Awaiting changes and removed awaiting change review Awaiting change review labels Apr 28, 2024
@jonkeane
Copy link
Member Author

Should we also bump the minimum version of R in the DESCRIPTION? Based on the removal of the str2lang backport, we require at least 3.6 now? That said, str2lang is only used if you call quantile() in summarize(), so not practically an issue for most.

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 github-actions bot added awaiting change review Awaiting change review and removed awaiting changes Awaiting changes labels Apr 28, 2024
@jonkeane
Copy link
Member Author

@github-actions crossbow submit r-binary-packages test-r-linux-valgrind

Copy link

Revision: 8d91cab

Submitted crossbow builds: ursacomputing/crossbow @ actions-bb446802ac

Task Status
r-binary-packages GitHub Actions
test-r-linux-valgrind GitHub Actions

@jonkeane
Copy link
Member Author

@github-actions crossbow submit r-binary-packages

Copy link

Revision: 67941ba

Submitted crossbow builds: ursacomputing/crossbow @ actions-437d88c30f

Task Status
r-binary-packages GitHub Actions

dev/tasks/tasks.yml Outdated Show resolved Hide resolved
@assignUser
Copy link
Member

Wow, this balloned, thanks @jonkeane! A minor thing we can do in a follow up imo is dropping the centos7 builds as libarrow is dropping support for that too #41395 (or maybe we can do it in that PR).

@assignUser
Copy link
Member

@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!

@jonkeane
Copy link
Member Author

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

Copy link

Revision: 8cad637

Submitted crossbow builds: ursacomputing/crossbow @ actions-c2f5ac8f88

Task Status
r-binary-packages GitHub Actions

@assignUser
Copy link
Member

assignUser commented Apr 29, 2024

@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.

@jonkeane jonkeane merged commit 6eb0b37 into apache:main Apr 29, 2024
57 of 60 checks passed
@jonkeane jonkeane removed the awaiting change review Awaiting change review label Apr 29, 2024
raulcd pushed a commit that referenced this pull request Apr 29, 2024
….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>
Copy link

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.

tolleybot pushed a commit to tmct/arrow that referenced this pull request May 2, 2024
…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>
vibhatha pushed a commit to vibhatha/arrow that referenced this pull request May 25, 2024
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI][R]: Update our backwards compatibility CI any other R 4.4 cleanups
3 participants