Process completed with exit code 1.

Command ['python', '-m', 'pip', 'wheel', PurePosixPath('/project/python'), '--wheel-dir=/tmp/cibuildwheel/built_wheel', '--no-deps', '-vvv'] failed with code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

libomp 22.1.1 is already installed and up-to-date. To reinstall 22.1.1, run: brew reinstall libomp

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

libomp 22.1.1 is already installed and up-to-date. To reinstall 22.1.1, run: brew reinstall libomp

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

libomp 22.1.1 is already installed and up-to-date. To reinstall 22.1.1, run: brew reinstall libomp

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

libomp 22.1.1 is already installed and up-to-date. To reinstall 22.1.1, run: brew reinstall libomp

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

libomp 22.1.1 is already installed and up-to-date. To reinstall 22.1.1, run: brew reinstall libomp

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

libomp 22.1.1 is already installed and up-to-date. To reinstall 22.1.1, run: brew reinstall libomp

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

libomp 22.1.1 is already installed and up-to-date. To reinstall 22.1.1, run: brew reinstall libomp

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

libomp 22.1.1 is already installed and up-to-date. To reinstall 22.1.1, run: brew reinstall libomp

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No files were found with the provided path: python/wheelhouse/*.whl python/dist/*.whl. No artifacts will be uploaded.