nealrichardson commented on PR #13464:
URL: https://github.com/apache/arrow/pull/13464#issuecomment-1172894011
Indications that this is working as expected:
* In the `r-binary-packages` workflow, I've edited the `test-linux-binary`
job to test both the automatic binary downloading behavior for some images
(`LIBARROW_BINARY` unset) and the opt-in by setting `LIBARROW_BINARY=true` on
OSes that aren't in the allowlist.
* For CentOS 7, we see the "Some features are not available with gcc 4"
message, and then success using the centos-7 binary
https://github.com/ursacomputing/crossbow/runs/7158493032?check_suite_focus=true#step:12:1170
* `rocker/r-ver:3.6.3` is Debian, so we set `LIBARROW_BINARY=true` and
it detects libcurl and openssl 1, and uses ubuntu-18.04
https://github.com/ursacomputing/crossbow/runs/7158493078?check_suite_focus=true#step:12:490
* `rocker/r-ubuntu:22.04` finds openssl3 so uses the ubuntu-22.04
binary:
https://github.com/ursacomputing/crossbow/runs/7158493225?check_suite_focus=true#step:12:489
* etc.
* In the [as-cran
workflow](https://github.com/ursacomputing/crossbow/actions/runs/2598400161),
all jobs say "Building libarrow from source", and none of them show any of the
messages from the code that tries to find system requirements to determine a
binary to download. (Even if they did try to download, the messages it prints
are generic enough not to broadcast it, and we would be fine as long as the
build succeeded.)
* We can spot-check the other builds to see which binary they would have
used if it existed--only the `r-binary-packages` workflow has the binary repo
set up, but unless we set `LIBARROW_BINARY=false`, the other jobs will still
try to find one.
Remaining to-dos:
* I'd like to add a few more docker images to the `test-linux-binary` job in
the packages workflow, just to confirm that the binaries are working across a
broader spectrum of system configurations.
* Installation vignette needs revision
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
