Skip to content

Build and Publish

Build and Publish #17

Manually triggered May 6, 2026 08:44
Status Failure
Total duration 33m 1s
Artifacts 1

pypi_publish.yml

on: workflow_dispatch
Matrix: build_wheels
publish
publish
Fit to window
Zoom out
Zoom in

Annotations

6 errors, 6 warnings, and 1 notice
Build cuda on ubuntu-latest
Process completed with exit code 1.
Build cuda on ubuntu-latest
'/opt/python/cp38-cp38/bin/python' executable doesn't exist in image 'nvidia/cuda:11.8.0-devel-centos7' to build 'cp38-manylinux_x86_64'.
Build cpu on ubuntu-latest
Process completed with exit code 1.
Build cpu on ubuntu-latest
Command ['sh', '-c', 'tmpdir=$(mktemp -d) && unzip -q /tmp/cibuildwheel/built_wheel/rapidspeech-0.0.0.dev0-cp38-cp38-linux_x86_64.whl -d $tmpdir && for f in $(find $tmpdir -name \'*.so\'); do\n patchelf --set-rpath \'$ORIGIN\' $f 2>/dev/null || true;\n for lib in libggml-base libggml-cpu libggml; do\n patchelf --replace-needed "ggml/src/$lib.so" "$lib.so" $f 2>/dev/null || true;\n done;\ndone && (cd $tmpdir && zip -qr /tmp/cibuildwheel/built_wheel/rapidspeech-0.0.0.dev0-cp38-cp38-linux_x86_64.whl .) && rm -rf $tmpdir && auditwheel repair -w /tmp/cibuildwheel/repaired_wheel /tmp/cibuildwheel/built_wheel/rapidspeech-0.0.0.dev0-cp38-cp38-linux_x86_64.whl\n'] failed with code 127.
Build metal on macos-latest
Process completed with exit code 1.
Build metal on macos-latest
Command delocate-wheel --require-archs arm64 -w /private/var/folders/tb/y368xp_x10s3ty1b_mtl5mxr0000gn/T/cibw-run-hk4xjwkg/cp38-macosx_arm64/repaired_wheel -v /private/var/folders/tb/y368xp_x10s3ty1b_mtl5mxr0000gn/T/cibw-run-hk4xjwkg/cp38-macosx_arm64/built_wheel/rapidspeech_metal-0.0.0.dev0-cp38-cp38-macosx_11_0_arm64.whl failed with code 1.
Build cuda on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@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/
Build cpu on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@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/
Build metal on macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@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/
Build cuda on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, jimver/cuda-toolkit@v0.2.20. 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/
Build cuda on windows-latest
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0dv/6aQAAAAC12Cxy4QphTIuELiqVOvAlREVOMzAxMDAwMTA3MDMzAEVkZ2U=
Build cuda on windows-latest
Failed to restore: Cache service responded with 400
Build cuda on windows-latest
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
wheels-cuda-windows-latest
18 MB
sha256:dafe5ad9d22566758af1004ab58a3874a30cf8fd70503f5f339b8de57ed3f0b3