TEST: arrow v23.0.0 (end-to-end)#1664
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12749814205. Examine the logs at this URL for more detail. |
|
This seems deprecated (as has already been done). I am closing it, feel free to reopen if necessary. |
|
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict. Please ping the 'conda-forge/core' team (using the |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16213744741. Examine the logs at this URL for more detail. |
|
arrow v20.0.0-rc0 is looking good from the POV of conda-forge! 🥳 @raulcd @kou @pitrou @jorisvandenbossche @assignUser |
|
@h-vetinari we have split I was planning to do some work there but I wanted to give you a heads up in case you start working on it |
|
The current failures seem related to the fix we had to apply to arrow-cpp, right? |
|
Yeah, CI here is outdated; I'll rebase and pick the changes from #1886 once CI there is through |
45f8252 to
3a05a2f
Compare
…6.01.23.17.07.14 Other tools: - conda-build 25.11.1 - rattler-build 0.55.0 - rattler-build-conda-compat 1.4.10
…6.01.24.04.42.29 Other tools: - conda-build 25.11.1 - rattler-build 0.55.0 - rattler-build-conda-compat 1.4.10
Some changes require testing across both libarrow and pyarrow; since we split off the pyarrow builds in a66c7c6, we'd need to publish a changed
libarrow, test the changes in pyarrow, and then potentially mark the builds as broken. In order to simplify this process, reintroduce some end-to-end testing here that can be used to do this all in one PR.Continued from #1432