Skip to content

Conversation

@jorisvandenbossche
Copy link
Member

@jorisvandenbossche jorisvandenbossche commented Apr 7, 2021

(I am first trying with linux)

@jorisvandenbossche
Copy link
Member Author

@github-actions crossbow submit -g conda

@github-actions
Copy link

github-actions bot commented Apr 7, 2021

@github-actions
Copy link

github-actions bot commented Apr 7, 2021

Revision: 83b91bf34161bcfef9c5449c2d9161fe80477233

Submitted crossbow builds: ursacomputing/crossbow @ actions-275

Task Status
conda-clean Azure
conda-linux-gcc-py36-aarch64 Drone
conda-linux-gcc-py36-cpu-r36 Azure
conda-linux-gcc-py36-cuda Azure
conda-linux-gcc-py37-aarch64 Drone
conda-linux-gcc-py37-cpu-r40 Azure
conda-linux-gcc-py37-cuda Azure
conda-linux-gcc-py38-aarch64 Drone
conda-linux-gcc-py38-cpu Azure
conda-linux-gcc-py38-cuda Azure
conda-linux-gcc-py39-aarch64 Drone
conda-linux-gcc-py39-cpu Azure
conda-linux-gcc-py39-cuda Azure
conda-osx-clang-py36-r36 Azure
conda-osx-clang-py37-r40 Azure
conda-osx-clang-py38 Azure
conda-osx-clang-py39 Azure
conda-win-vs2017-py36-r36 Azure
conda-win-vs2017-py37-r40 Azure
conda-win-vs2017-py38 Azure

@jorisvandenbossche
Copy link
Member Author

@github-actions crossbow submit conda-linux-gcc-py38-cpu

@github-actions
Copy link

github-actions bot commented Apr 7, 2021

Revision: 70a18ef102ef146c100865a30807f7d7875cb4ad

Submitted crossbow builds: ursacomputing/crossbow @ actions-276

Task Status
conda-linux-gcc-py38-cpu Azure

@xhochy
Copy link
Member

xhochy commented Apr 8, 2021

@github-actions crossbow submit conda-linux-gcc-py38-cpu

@github-actions
Copy link

github-actions bot commented Apr 8, 2021

Revision: 985951ee3eff85a713d4518441715a5732803ae0

Submitted crossbow builds: ursacomputing/crossbow @ actions-284

Task Status
conda-linux-gcc-py38-cpu Azure

@jorisvandenbossche
Copy link
Member Author

I suppose that in the past we made some adjustments to the build scripts (run_docker_build.sh) after copying them from upstream conda-forge, to make it work here? (cc @kszucs)
If that's the case, it would be good to better document that / more clearly separate those changes (so they can be applied later again).

@jorisvandenbossche
Copy link
Member Author

@xhochy
Copy link
Member

xhochy commented Apr 8, 2021

@jorisvandenbossche I would revert the changes to dev/tasks/conda-recipes/{run_docker_build.sh,build_steps.sh} and put a comment at the top that we did modify them manually. We shouldn't need to update them. Also I would have a bit of time today to finish this PR, ok if I take this over from you?

@jorisvandenbossche
Copy link
Member Author

ok if I take this over from you?

Sure!

@xhochy
Copy link
Member

xhochy commented Apr 8, 2021

@github-actions crossbow submit conda-linux-gcc-py38-cpu

@kszucs
Copy link
Member

kszucs commented Apr 8, 2021

Note that I have a large undertaking for crossbow #9913 which I plan to merge today, so expect for some minor conflicts.

@xhochy Just an idea: could we clone the upstream conda-forge repository in the crossbow task instead of vendoring the files? We would need to vendor a couple of fines to enable us introducing modifying dependencies, but this approach could help to keep the setup in sync with the feedstock.

@xhochy
Copy link
Member

xhochy commented Apr 8, 2021

Note that I have a large undertaking for crossbow #9913 which I plan to merge today, so expect for some minor conflicts.

I don't see any conflicting things here, so I would hope that a rebase here will work out fine. Thanks for the heads-up 👍

@xhochy Just an idea: could we clone the upstream conda-forge repository in the crossbow task instead of vendoring the files? We would need to vendor a couple of fines to enable us introducing modifying dependencies, but this approach could help to keep the setup in sync with the feedstock.

Yes, that could be part of a future solution. I'm currently struggling a bit with it though as the number of possible conda configurations varies on conda-forge and the names of the files in .ci_support changes quite often. Furthermore, it would be nice to have a libarrow recipe that is the base for both the Python and R packages but doesn't depend on Python. This would need a bit more of a restructuring inside the arrow codebase.

@github-actions
Copy link

github-actions bot commented Apr 8, 2021

Revision: 91b780510a57150d89588b8cb7f9285a9683ff16

Submitted crossbow builds: ursacomputing/crossbow @ actions-291

Task Status
conda-linux-gcc-py38-cpu Azure

@xhochy
Copy link
Member

xhochy commented Apr 8, 2021

@github-actions crossbow submit -g conda

@github-actions
Copy link

github-actions bot commented Apr 8, 2021

Revision: 82b5d5a1c685b90595e9ad013a7c7b341c527d2c

Submitted crossbow builds: ursacomputing/crossbow @ actions-298

Task Status
conda-clean Azure
conda-linux-gcc-py36-aarch64 Drone
conda-linux-gcc-py36-cpu-r36 Azure
conda-linux-gcc-py36-cuda Azure
conda-linux-gcc-py37-aarch64 Drone
conda-linux-gcc-py37-cpu-r40 Azure
conda-linux-gcc-py37-cuda Azure
conda-linux-gcc-py38-aarch64 Drone
conda-linux-gcc-py38-cpu Azure
conda-linux-gcc-py38-cuda Azure
conda-linux-gcc-py39-aarch64 Drone
conda-linux-gcc-py39-cpu Azure
conda-linux-gcc-py39-cuda Azure
conda-osx-arm64-clang-py38 Azure
conda-osx-arm64-clang-py39 Azure
conda-osx-clang-py36-r36 Azure
conda-osx-clang-py37-r40 Azure
conda-osx-clang-py38 Azure
conda-osx-clang-py39 Azure
conda-win-vs2017-py36-r36 Azure
conda-win-vs2017-py37-r40 Azure
conda-win-vs2017-py38 Azure

@xhochy
Copy link
Member

xhochy commented Apr 9, 2021

@github-actions crossbow submit conda-win-*

@github-actions
Copy link

github-actions bot commented Apr 9, 2021

Revision: 989900a7c56a05826195d18462e8fa79511d8e31

Submitted crossbow builds: ursacomputing/crossbow @ actions-301

Task Status
conda-win-vs2017-py36-r36 Azure
conda-win-vs2017-py37-r40 Azure
conda-win-vs2017-py38 Azure
conda-win-vs2017-py39 Azure

@xhochy
Copy link
Member

xhochy commented Apr 9, 2021

@jorisvandenbossche @kszucs This is ready for review, updated all x86 conda packages and sneaked in builds for the Apple M1.

@xhochy
Copy link
Member

xhochy commented Apr 9, 2021

One of the Windows builds progressed so far on my crossbow that I'm confident that the rest will also be green in ~1h: https://dev.azure.com/mail0406/crossbow/_build/results?buildId=26&view=logs&j=4c86bc1b-1091-5192-4404-c74dfaad23e7&t=41795ef0-6501-5db4-3ad4-33c0cf085626

@xhochy xhochy force-pushed the ARROW-12246-conda-recipes branch from 989900a to f337001 Compare April 12, 2021 13:01
@xhochy
Copy link
Member

xhochy commented Apr 12, 2021

@github-actions crossbow submit -g conda

@github-actions
Copy link

Revision: f337001

Submitted crossbow builds: ursacomputing/crossbow @ actions-310

Task Status
conda-clean Azure
conda-linux-gcc-py36-arm64 Drone
conda-linux-gcc-py36-cpu-r36 Azure
conda-linux-gcc-py36-cuda Azure
conda-linux-gcc-py37-arm64 Drone
conda-linux-gcc-py37-cpu-r40 Azure
conda-linux-gcc-py37-cuda Azure
conda-linux-gcc-py38-arm64 Drone
conda-linux-gcc-py38-cpu Azure
conda-linux-gcc-py38-cuda Azure
conda-linux-gcc-py39-arm64 Drone
conda-linux-gcc-py39-cpu Azure
conda-linux-gcc-py39-cuda Azure
conda-osx-arm64-clang-py38 Azure
conda-osx-arm64-clang-py39 Azure
conda-osx-clang-py36-r36 Azure
conda-osx-clang-py37-r40 Azure
conda-osx-clang-py38 Azure
conda-osx-clang-py39 Azure
conda-win-vs2017-py36-r36 Azure
conda-win-vs2017-py37-r40 Azure
conda-win-vs2017-py38 Azure
conda-win-vs2017-py39 Azure

Copy link
Member Author

@jorisvandenbossche jorisvandenbossche left a comment

Choose a reason for hiding this comment

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

Thanks for finishing this! Assuming the builds pass, this is all good for me.
I just added two suggestions of adding some more comments for our future selves (I commented on a subset of the diff, to see the changes after updating with the upstream version, but could be I was looking at wrong changes;)).

copy /Y "%SRC_DIR%\cpp\cmake_modules\CompilerInfo.cmake" cmake_modules\
copy /Y "%SRC_DIR%\cpp\cmake_modules\FindNumPy.cmake" cmake_modules\
copy /Y "%SRC_DIR%\cpp\cmake_modules\FindPythonLibsNew.cmake" cmake_modules\
@rem del cmake_modules\BuildUtils.cmake
Copy link
Member Author

Choose a reason for hiding this comment

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

Worth adding a comment that those are commented out compared to the upstream conda-forge build script?

@@ -1,6 +1,6 @@
{% set version = "3.0.0" %}
{% set version = ARROW_VERSION %}
Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe can add a comment here indicating that setting this to ARROW_VERSION is a difference compared to the upstream version?

@xhochy xhochy closed this in c394a20 Apr 15, 2021
@jorisvandenbossche jorisvandenbossche deleted the ARROW-12246-conda-recipes branch June 2, 2022 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants