WIP: [Release] Verify release-10.0.1-rc0 #14654
Conversation
|
@github-actions crossbow submit --group verify-rc-source --param release=10.0.1 --param rc=0 |
|
Revision: a6eabc2 Submitted crossbow builds: ursacomputing/crossbow @ actions-36c520c6c6
|
|
Revision: a6eabc2 Submitted crossbow builds: ursacomputing/crossbow @ release-10.0.1-rc0-0
|
|
@nealrichardson @paleolimbot @thisisnic r-binary-packages failed. Could you confirm this? Note that the same error is happen on master too: https://github.com/ursacomputing/crossbow/actions/runs/3468776645/jobs/5795178913 |
|
Weird, that error is triggered when the C++ library hasn't been built with enough functionality to support the R package, so I'd expect it to be something odd happening with the CI rather than a code change. I've re-triggered the job to make sure it's not some transient issue. |
|
Hmm, failed again almost immediately: https://github.com/ursacomputing/crossbow/actions/runs/3475288883/jobs/5817793906 I'm not sure what's going on there. @assignUser - anything jump out at you there? |
|
@thisisnic seems to be an issue with the rocker image overriding the repo settings and forcefull installing the packages via apt and thus installing We might need/want to replace that image to stop that. Should not matter for this release though 👍 |
If the test is failed, R binaries aren't uploaded: https://github.com/ursacomputing/crossbow/actions/runs/3475288883/jobs/5809989647 Is it OK for R? If it's OK, I'll continue with the failure. |
This seems to be due to @eddelbuettel Did you push the image to DockerHub without updating the Dockerfile on GitHub? |
|
@eitsupi If so then only by accident. But I did 'batch' update a few (layered) containers following the R 4.2.2 release and may inadvertendly (by doing this manually) crossed 'tags' and Dockerfiles. Building and pushing a new image '22.04' (also as 'jammy') now. And yes, you are correct: |
|
@eitsupi Thanks for the information! Do you know Docker images that can be replaced with https://github.com/apache/arrow/blob/master/dev/tasks/r/github.packages.yml#L247-L250 ? |
I think As for However, the update mechanism of |
|
@kou "It's complicated." @eitsupi and I are both behind Rocker, and these choices present two different and not exactly interchangeable options with different settings. So in two characters: "no". In more words: "it depends, they both have their (different) use cases". I do all my CI with r-ubuntu / r-bspm / r2u as I want current toolchains and current CRAN easily. YMMV. |
And if so, has been fixed. Did you try the container I uploaded ~20 mins ago? |
I'll re-run the job |
I pulled from DockerHub, but the digest does not seem to have changed.
|
|
My bad, in the rush I did which replaced one but not both of these. I skipped the build step for 22,04 Will ship and update 22.04 tag in a minute or two -- now building. |
|
Rebuilt and repushed. I used edd@rob:~/git/rocker-ubuntu-lts/jammy(master)$ docker images |head -3
REPOSITORY TAG IMAGE ID CREATED SIZE
rocker/r-ubuntu jammy 7214e2c7ed54 7 minutes ago 743MB
rocker/r-ubuntu 22.04 091427e0bcf7 11 minutes ago 743MB
edd@rob:~/git/rocker-ubuntu-lts/jammy(master)$ |
|
@eitsupi Sorry! I misunderstood. @eddelbuettel Thanks! It worked: https://github.com/ursacomputing/crossbow/actions/runs/3468776645/jobs/5828688028 |
|
@github-actions crossbow submit --group verify-rc-binaries --group verify-rc-wheels --param release=10.0.1 --param rc=0 |
|
Revision: a6eabc2 Submitted crossbow builds: ursacomputing/crossbow @ actions-96463f290f
|
5 participants
PR to verify Release Candidate