GH-49566: [Python] Skip header files when installing compiled Cython files and other Python release verification fixes#49571
Conversation
|
|
|
@github-actions crossbow submit verify-rc-source-python-* |
|
Revision: 719eaf2 Submitted crossbow builds: ursacomputing/crossbow @ actions-3593c891fd |
|
macOS failure are unrelated, I am trying to find a fix, the issue tracking them is this one: |
|
We have a different issue now: _____________________________ test_pyarrow_include _____________________________
def test_pyarrow_include():
# We need to make sure that pyarrow/include is always
# created. Either with PyArrow C++ header files or with
# Arrow C++ and PyArrow C++ header files together
source = os.path.dirname(os.path.abspath(__file__))
pyarrow_dir = pjoin(source, '..')
pyarrow_include = pjoin(pyarrow_dir, 'include')
pyarrow_cpp_include = pjoin(pyarrow_include, 'arrow', 'python')
> assert os.path.exists(pyarrow_include)
E AssertionError: assert False
E + where False = <function exists at 0x7ff433ef9e80>('/arrow/python/pyarrow/tests/../include')
E + where <function exists at 0x7ff433ef9e80> = <module 'posixpath' (frozen)>.exists
E + where <module 'posixpath' (frozen)> = os.pathInvestigating ... |
|
@github-actions crossbow submit verify-rc-source-python-* |
|
Revision: 9ba4a76 Submitted crossbow builds: ursacomputing/crossbow @ actions-7e817c381a |
|
Another issue I need to investigate: |
|
@github-actions crossbow submit verify-rc-source-python-macos-arm64 |
|
Testing if it is a flaky macos issue ... |
|
Revision: 9ba4a76 Submitted crossbow builds: ursacomputing/crossbow @ actions-49b32e9b3a
|
|
@github-actions crossbow submit verify-rc-source-python-macos-amd64 |
|
Revision: 9ba4a76 Submitted crossbow builds: ursacomputing/crossbow @ actions-109f022a4d
|
|
cc @raulcd for ideas? (can't test locally, my chip is arm) |
9ba4a76 to
3f0f110
Compare
|
@github-actions crossbow submit verify-rc-source-python-macos-amd64 verify-rc-source-python-macos-arm64 |
|
@AlenkaF I've rebased main (the macOS arm64 should be fixed there, just validating now) and have pushed a new commit because I think the verification wasn't correct. Is not using the built virtualenv/conda env. I am unsure what the macOS Intel failure is but the reason doesn't seem to be the same one as the one for the other failures so we might want to tackle that one on a separate issue. |
|
Revision: 3f0f110 Submitted crossbow builds: ursacomputing/crossbow @ actions-b16e795f8d
|
|
Python 3.14 verification on macos arm is now failing due to: update: both builds have the same, above, issue now 👍 |
|
Revision: 5f8c18c Submitted crossbow builds: ursacomputing/crossbow @ actions-e5fbc461ef
|
|
@github-actions crossbow submit verify-rc-source-python-macos-amd64 |
|
|
@github-actions crossbow submit verify-rc-source-python-macos-amd64 |
|
Revision: a5ff56d Submitted crossbow builds: ursacomputing/crossbow @ actions-0c439b7c1c
|
|
@github-actions crossbow submit verify-rc-source-python-* |
|
Revision: f9ca17b Submitted crossbow builds: ursacomputing/crossbow @ actions-fd39c8b507 |
|
|
||
| # Build pyarrow | ||
| python -m pip install -e . | ||
| python -m pip install --no-build-isolation . |
There was a problem hiding this comment.
For the release verification of Python. I am unsure why we were testing with build isolation. We are setting up a virtualenv or a conda env and we should use that, that's why I am adding the --no-build-isolation. Also I am unsure why we were testing with editable builds. That doesn't make much sense for verification.
There was a problem hiding this comment.
I agree with you, looks OK to me now.
|
@raulcd the changes LGTM, thank you! |
|
|
||
| # Build pyarrow | ||
| python -m pip install -e . | ||
| python -m pip install --no-build-isolation . |
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 2c2a61c. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 8 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…ython files and other Python release verification fixes (apache#49571) ### Rationale for this change Local import is broken when doing editable install with scikit-build-core, also nightly verification jobs are failing for the same reason. ### What changes are included in this PR? - `lib.h` and `lib_api.h` are already installed separately so we skip them when installing Cython extensions into the output destination (`side-packages/pyarrow`). - Arrow library directory is added to the `RPATH`, in the case of not bundling ARROW_CPP, to fix linking issues on macos - `test_pyarrow_include` is updated due to compiled files now being moved to the site-packages - updates to the release verification script when building pyarrow - update of `brew` on the "Install System Dependencies" step in the rc verification job to fix an issue with protobuf mixed versions ### Are these changes tested? Yes, locally and via the extended verification builds. ### Are there any user-facing changes? No. * GitHub Issue: apache#49566 Lead-authored-by: Raúl Cumplido <raulcumplido@gmail.com> Co-authored-by: AlenkaF <frim.alenka@gmail.com> Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
…ython files and other Python release verification fixes (apache#49571) ### Rationale for this change Local import is broken when doing editable install with scikit-build-core, also nightly verification jobs are failing for the same reason. ### What changes are included in this PR? - `lib.h` and `lib_api.h` are already installed separately so we skip them when installing Cython extensions into the output destination (`side-packages/pyarrow`). - Arrow library directory is added to the `RPATH`, in the case of not bundling ARROW_CPP, to fix linking issues on macos - `test_pyarrow_include` is updated due to compiled files now being moved to the site-packages - updates to the release verification script when building pyarrow - update of `brew` on the "Install System Dependencies" step in the rc verification job to fix an issue with protobuf mixed versions ### Are these changes tested? Yes, locally and via the extended verification builds. ### Are there any user-facing changes? No. * GitHub Issue: apache#49566 Lead-authored-by: Raúl Cumplido <raulcumplido@gmail.com> Co-authored-by: AlenkaF <frim.alenka@gmail.com> Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
Rationale for this change
Local import is broken when doing editable install with scikit-build-core, also nightly verification jobs are failing for the same reason.
What changes are included in this PR?
lib.handlib_api.hare already installed separately so we skip them when installing Cython extensions into the output destination (side-packages/pyarrow).RPATH, in the case of not bundling ARROW_CPP, to fix linking issues on macostest_pyarrow_includeis updated due to compiled files now being moved to the site-packagesbrewon the "Install System Dependencies" step in the rc verification job to fix an issue with protobuf mixed versionsAre these changes tested?
Yes, locally and via the extended verification builds.
Are there any user-facing changes?
No.