Command ['sh', '-c', 'yum update -y && yum install -y glibc-devel wget python3-devel'] failed with code 127.

Process completed with exit code 1.

The job was canceled because "ubuntu-24_04_311" failed.

Command ['sh', '-c', 'yum update -y && yum install -y glibc-devel wget python3-devel'] failed with code 127.

The operation was canceled.

The job was canceled because "ubuntu-24_04_311" failed.

The operation was canceled.

The job was canceled because "ubuntu-24_04_311" failed.

The operation was canceled.

The job was canceled because "ubuntu-24_04_311" failed.

The job was canceled because "ubuntu-24_04_311" failed.

The operation was canceled.

The operation was canceled.

The job was canceled because "ubuntu-24_04_311" failed.

The operation was canceled.

The job was canceled because "ubuntu-24_04_311" failed.

The operation was canceled.

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

cmake 3.31.1 is already installed and up-to-date. To reinstall 3.31.1, run: brew reinstall cmake

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (10.13).

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (11.0).

While arm64 wheels can be built on x86_64, they cannot be tested. Consider building arm64 wheels natively, if your CI provider offers this. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_arm64"`.

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (10.13).

While universal2 wheels can be built on x86_64, the arm64 part of the wheel cannot be tested on x86_64. Consider building universal2 wheels on an arm64 runner, if your CI provider offers this. Notably, an arm64 runner can also test the x86_64 part of the wheel, through Rosetta emulation. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_universal2:arm64"`.

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (10.13).

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (11.0).

While arm64 wheels can be built on x86_64, they cannot be tested. Consider building arm64 wheels natively, if your CI provider offers this. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_arm64"`.

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (10.13).

While universal2 wheels can be built on x86_64, the arm64 part of the wheel cannot be tested on x86_64. Consider building universal2 wheels on an arm64 runner, if your CI provider offers this. Notably, an arm64 runner can also test the x86_64 part of the wheel, through Rosetta emulation. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_universal2:arm64"`.

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (11.0).

While arm64 wheels can be built on x86_64, they cannot be tested. Consider building arm64 wheels natively, if your CI provider offers this. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_arm64"`.

While universal2 wheels can be built on x86_64, the arm64 part of the wheel cannot be tested on x86_64. Consider building universal2 wheels on an arm64 runner, if your CI provider offers this. Notably, an arm64 runner can also test the x86_64 part of the wheel, through Rosetta emulation. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_universal2:arm64"`.

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (11.0).

While arm64 wheels can be built on x86_64, they cannot be tested. Consider building arm64 wheels natively, if your CI provider offers this. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_arm64"`.

While universal2 wheels can be built on x86_64, the arm64 part of the wheel cannot be tested on x86_64. Consider building universal2 wheels on an arm64 runner, if your CI provider offers this. Notably, an arm64 runner can also test the x86_64 part of the wheel, through Rosetta emulation. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_universal2:arm64"`.

While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.

While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.

While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.

While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.

While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (11.0).

While arm64 wheels can be built on x86_64, they cannot be tested. Consider building arm64 wheels natively, if your CI provider offers this. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_arm64"`.

While universal2 wheels can be built on x86_64, the arm64 part of the wheel cannot be tested on x86_64. Consider building universal2 wheels on an arm64 runner, if your CI provider offers this. Notably, an arm64 runner can also test the x86_64 part of the wheel, through Rosetta emulation. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_universal2:arm64"`.

Bumping MACOSX_DEPLOYMENT_TARGET (10.11) to the minimum required (11.0).

While arm64 wheels can be built on x86_64, they cannot be tested. Consider building arm64 wheels natively, if your CI provider offers this. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_arm64"`.

While universal2 wheels can be built on x86_64, the arm64 part of the wheel cannot be tested on x86_64. Consider building universal2 wheels on an arm64 runner, if your CI provider offers this. Notably, an arm64 runner can also test the x86_64 part of the wheel, through Rosetta emulation. To silence this warning, set `CIBW_TEST_SKIP: "*-macosx_universal2:arm64"`.

Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-yiemismt\cp39-win_arm64\build\extra-setup.cfg for cross-compilation

Setting SETUPTOOLS_EXT_SUFFIX=.cp39-win_arm64.pyd for cross-compilation

Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation

Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation

Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-hog3o8z_\cp311-win_arm64\build\extra-setup.cfg for cross-compilation

Setting SETUPTOOLS_EXT_SUFFIX=.cp311-win_arm64.pyd for cross-compilation

Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation

Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation

Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-jrs238cr\cp313-win_arm64\build\extra-setup.cfg for cross-compilation

Setting SETUPTOOLS_EXT_SUFFIX=.cp313-win_arm64.pyd for cross-compilation

Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation

Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation

Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-dm0zptvf\cp310-win_arm64\build\extra-setup.cfg for cross-compilation

Setting SETUPTOOLS_EXT_SUFFIX=.cp310-win_arm64.pyd for cross-compilation

Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation

Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation

Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-bvf9dvhb\cp312-win_arm64\build\extra-setup.cfg for cross-compilation

Setting SETUPTOOLS_EXT_SUFFIX=.cp312-win_arm64.pyd for cross-compilation

Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation

Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation

Setting SYSTEM_VERSION_COMPAT=0 to ensure CPython 3.8 can get correct macOS version and allow installation of wheels with MACOSX_DEPLOYMENT_TARGET >= 11.0. See https://github.com/pypa/cibuildwheel/issues/1767 for the details.