WIP: Dummy PR to check maint-18.0.0 status #44367
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…44359) ### Rationale for this change This is not happen on Debian GNU/Linux stable and unstable. This is happen only on Debian GNU/Linux testing. So this may be a temporary problem. ### What changes are included in this PR? Create a non-existent path manually as a workaround. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * GitHub Issue: #44358 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
### Rationale for this change Other file systems such as GCS file system and S3 file system are enabled. ### What changes are included in this PR? Enabled Azure file system. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * GitHub Issue: #44347 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…n wheel-manylinux-*-cp313t-* (#44362) ### Rationale for this change If interactive deb configuration is used, CI is blocked by waiting an user input. ### What changes are included in this PR? Disable interactive deb configuration. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: #44355 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
…ckaging (#44148) ## WIP Creating the PR to validate if / what are the CI failures ### Rationale for this change Once the issue has been merged: - #25118 We do not require numpy as a pyarrow dependency. ### What changes are included in this PR? Remove numpy as a required dependency ### Are these changes tested? Via CI ### Are there any user-facing changes? Yes, pyarrow won't install numpy as a required dependency. * GitHub Issue: #43846 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…test wheels on Python 3.13 (#44193) ### Rationale for this change Now that numpy, cython and pandas all have releases that support Python 3.13, we can remove the extra index and ensure that we are building our wheels with the released version instead of nightly dev version. * GitHub Issue: #43519 Authored-by: Joris Van den Bossche <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…test_dataset.py (#44370) ### Rationale for this change If pyarrow has been built without dataset test collection errors due to pytest.mark.parametrize requiring dataset. ### What changes are included in this PR? Move dataset requirement outside of test collection by removing it from the parametrization. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: #44369 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…ve macOS 12 pyarrow wheels (#44315) ### Rationale for this change We did just bump MACOSX_DEPLOYMENT_TARGET from 10 to 12 for pyarrow wheels on 18.0.0, we probably should wait a little before dropping. ### What changes are included in this PR? Revert moving macOS deployment target to 12 ### Are these changes tested? Will trigger wheel jobs on archery ### Are there any user-facing changes? Yes, wheels will be available for macOS 12. * GitHub Issue: #44314 Authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…4374) ### Rationale for this change Java-jars are currently failing on macOS to install Python 3.13 because `python@ 3.13` (`python` is an alias of `python@ 3.13` now) isn't installed yet. Our link failure workaround is updating already installed `python@*` with `--overwrite` explicitly. `python@ 3.13` (`python`) isn't installed on GitHub Actions runner yet. So `brew bundle` installs `python` without `--overwrite`. ### What changes are included in this PR? Install `python` with `--overwrite` explicitly before `brew bundle`. ### Are these changes tested? Via CI ### Are there any user-facing changes? No * GitHub Issue: #44373 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
### Rationale for this change When adding Python 3.13 support (#43539), conda was not yet ready to support Python 3.13. But over the last weeks most conda packages having being updated, so trying again. * GitHub Issue: #43519 Authored-by: Joris Van den Bossche <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
…cation jobs (#44382) ### Rationale for this change Verification job is currently failing for Ruby. ### What changes are included in this PR? We can't use Python 3.13 and `glib==2.80.5`. So we use old Python as a workaround. ### Are these changes tested? Via archery ### Are there any user-facing changes? No * GitHub Issue: #44381 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…fication when using Conda (#44388) ### Rationale for this change Conda Python 3.13 fails when running verification tasks for Java. It's related to JPype. See also: * GH-44389 * https://discuss.python.org/t/api-for-python-3-13-prevents-use-of-3rd-party-gc-allocators/62709/5 ### What changes are included in this PR? Pin Python 3.12 on Conda integration jobs because JPype doesn't work with Python 3.13. We can use Python 3.13 again once JPype supports Python 3.13. ### Are these changes tested? Yes via CI ### Are there any user-facing changes? No * GitHub Issue: #44386 Lead-authored-by: Raúl Cumplido <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
|
Revision: 0e184c3 Submitted crossbow builds: ursacomputing/crossbow @ tests-maint-18.0.0-1
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
### Rationale for this change jemalloc may have a problem on ARM. See also: #44342 ### What changes are included in this PR? * Disable jemalloc by default on ARM. * Disable jemalloc for manylinux wheel for ARM. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * GitHub Issue: #44342 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
This was referenced Oct 14, 2024
This comment was marked as outdated.
This comment was marked as outdated.
…rification script (#44407) ### Rationale for this change We can remove these pins now that conda-forge/glib-feedstock#191 has been closed. I've tested on my own crossbow and will test here momentarily. This effectively reverts #44270 and #44268. ### What changes are included in this PR? Tweaks to release release verification script, specifically removing recently-added pins. ### Are these changes tested? Yes: https://github.com/amoeba/crossbow/actions/runs/11335070956/job/31522511285. ### Are there any user-facing changes? No. Closes #44415. * GitHub Issue: #44415 Authored-by: Bryce Mecum <[email protected]> Signed-off-by: Bryce Mecum <[email protected]>
|
Revision: 70a2245 Submitted crossbow builds: ursacomputing/crossbow @ packaging-maint-18.0.0-2
|
|
Revision: 70a2245 Submitted crossbow builds: ursacomputing/crossbow @ release-maint-18.0.0-2
|
…44425) ### Rationale for this change It seems that the current `quay.io/centos/centos:stream9` for `linux/aarch64` is broken. We use it for building and testing but testing is only broken for now. Because we use cached (a bit old) `quay.io/centos/centos:stream9` for now. Building will be failed when the cache is expired. ### What changes are included in this PR? Change upload phase to after the build from after the test. Test is still failing but we can proceed our release process by this. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: #44422 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE.
This PR is to track some crossbow jobs to validate status of maintenance branch before creating the first RC.