GH-42111: [CI][Packaging] Re-synchronize conda_recipes with arrow-cpp-feedstock #42114
Conversation
|
@github-actions crossbow submit -g conda |
amoeba
changed the title
|
Revision: 6ce51d5 Submitted crossbow builds: ursacomputing/crossbow @ actions-1622970cbf
|
|
I initially thought this might be straightforward but after looking at past PRs, such as #37624, I see there's a bit more to it. @h-vetinari would you have any time to look at this? I've done a first pass and there's almost definitely more to do here so another set of eyes would be appreciated. |
| @@ -245,7 +245,7 @@ tasks: | |||
| ci: azure | |||
| template: conda-recipes/azure.linux.yml | |||
| params: | |||
| config: linux_64_cuda_compiler_versionNone | |||
| config: linux_64_c_compiler_version12c_stdlib_version2.12cuda_compilerNonecuda_compiler_versionNonecxx_compiler_version12 | |||
| artifacts: | |||
There was a problem hiding this comment.
My guess is that the number and names of artifacts have changed so I need to figure that out for all of these tasks.
github-actions
bot
added
awaiting committer review
|
So in general, what you'd need to do is:
In the case of this update, the split of the python outputs into a separate feedstock means you'll have to integrate a full third recipe here, and build the |
|
Thanks @h-vetinari, I did at least some of those steps after studying past PRs but will go over your list more thoroughly tomorrow. I did find I had to edit meta.yml in a few places to make it work here. Re: @kou's comment about scripting, it seems like we could probably do all of the above with a script plus maybe a few patchfiles for the arrow repo specifics. |
amoeba
force-pushed
the
sync-arrow-cpp-feedstocks
branch
from
6ce51d5
to
353c3fe
Compare
|
@github-actions crossbow submit -g conda |
|
Revision: 353c3fe Submitted crossbow builds: ursacomputing/crossbow @ actions-ba6a36d7ee
|
|
The current problem I see is that now that we did split |
|
I was doing some triaging + cleaning up of various jobs in our crossbow tests that are failing frequently. I've opened #43451 to temporarily disable running these every night so we don't continue getting alarmed while we work out what we need to do to synchronize these. I appreciate the work y'all are putting into getting these back up, and would happily close the temporary disabling PR if we can get these back running soon. |
There's some work ongoing to update the conda jobs #42114, but many of them have been failing for many days (some have no history of success in our [crossbow report](http://crossbow.voltrondata.com)). Let's turn those off temporarily so that we stop ignoring other failures alongside it, and we can re-enable them once we get them back running. Alternatively, we could merge those fixes and close this PR. * GitHub Issue: #43450 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
Rationale for this change
See #42111.
What changes are included in this PR?
Are these changes tested?
No, we need to test in CI.
Are there any user-facing changes?
No.