chore: prepare branch for 0.12.2 - #2567
Merged
Merged
Conversation
## Why? Golang xlang tests are failing because pyfory is not installed ## What does this PR do? * Add step to install the pyfory package in the CI workflow. * Ensure pyarrow, cython, wheel, pytest, and setuptools are up-to-date. ## Related issues Fixes apache#2555
CI was not reflecting failures in shell script fallbacks (we are migrating to python) * Use sys.exit() to propagate the return code from subprocess.call(). * This ensures that the CI pipeline correctly reflects the success or failure of the executed scripts. You might want to merge apache#2561 first, to reduce the number of errors. --------- Co-authored-by: chaokunyang <shawn.ck.yang@gmail.com>
chaokunyang
force-pushed
the
prepare_for_0.12.2
branch
from
September 3, 2025 02:43
1b3f6cf to
6c83e33
Compare
theweipeng
approved these changes
Sep 3, 2025
This file contains hidden or 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
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.
Why?
What does this PR do?
Related issues
Does this PR introduce any user-facing change?
Benchmark