The GitHub Actions job "Fory CI" on fory.git/main has succeeded. Run started by GitHub user chaokunyang (triggered by chaokunyang).
Head commit for run: c7cd3524add1f363aa6f5861682eb825c643357f / Emre Şafak <[email protected]> fix(ci): Build python wheels using interpreters in manylinux2014 (#2486) ## What does this PR do? The existing workflow did not build wheels correctly because the python interpreter installed in the workflow was not used in the container where the actual building was taking place. The manylinux images already have every python version pre-installed. We now use them instead. Key changes include: - **New Workflows:** - `build-containerized-pr.yml`: Handles building wheels for pull requests using containerized environments for Linux. - `build-containerized-release.yml`: Handles building wheels for releases using containerized environments for Linux. - `build-native-pr.yml`: Handles building wheels for pull requests on macOS and Windows. - `build-native-release.yml`: Handles building wheels for releases on macOS and Windows. - **Removed Workflows:** - `.github/workflows/build-wheels.yaml`: This generic workflow has been superseded by the new, more specific workflows. - `.github/workflows/build-wheels-for-pr.yaml`: Merged into `build-containerized-pr.yml` and `build-native-pr.yml`. - `.github/workflows/build-wheels-for-release.yaml`: Merged into `build-containerized-release.yml` and `build-native-release.yml`. - `.github/workflows/build-native-pr.yml`: This was a duplicate and is now handled by the new `build-native-pr.yml`. - **Script Improvements:** - `ci/build_linux_wheels.py`: Introduced a new script to manage Linux wheel building within Docker containers, replacing `build_manylinux_wheel.sh`. This script now uses explicit Docker image definitions and a simplified execution model. - `ci/deploy.sh`: Updated to use `PYTHON_PATH` and `PIP_CMD` for better Python environment management, and adjusted `pyarrow` installation versions for different Python versions. - `ci/run_ci.sh`: Updated to correctly handle Bazel installation paths (avoiding sudo) and use `curl` for downloading Bazel, since wget is not in the container. - **Workflow Triggers:** - Workflows are now triggered based on their intended purpose (e.g., `push` to `main` or tags for releases, `pull_request` events for PR builds). - Path filters have been adjusted to ensure workflows trigger only when relevant files are changed. ## Related issues Closes #2480 ## Notes I also attempted to create musl builds but they failed because the bazel binaries are incompatible with it. We would need to rebuild bazel for musllinux. Report URL: https://github.com/apache/fory/actions/runs/17058498663 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
