Skip to content

clean up macOS x86-64 workarounds in cibw_test_command.sh #16

clean up macOS x86-64 workarounds in cibw_test_command.sh

clean up macOS x86-64 workarounds in cibw_test_command.sh #16

Triggered via push July 6, 2025 18:18
Status Failure
Total duration 11m 8s
Artifacts 11

wheels.yml

on: push
Matrix: build_wheels
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Upload release to TestPyPI
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:rgommers/numpy-release:environment:pypi` * `repository`: `rgommers/numpy-release` * `repository_owner`: `rgommers` * `repository_owner_id`: `98330` * `workflow_ref`: `rgommers/numpy-release/.github/workflows/wheels.yml@refs/heads/main` * `job_workflow_ref`: `rgommers/numpy-release/.github/workflows/wheels.yml@refs/heads/main` * `ref`: `refs/heads/main` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Upload release to PyPI
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:rgommers/numpy-release:environment:pypi` * `repository`: `rgommers/numpy-release` * `repository_owner`: `rgommers` * `repository_owner_id`: `98330` * `workflow_ref`: `rgommers/numpy-release/.github/workflows/wheels.yml@refs/heads/main` * `job_workflow_ref`: `rgommers/numpy-release/.github/workflows/wheels.yml@refs/heads/main` * `ref`: `refs/heads/main` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Artifacts

Produced during runtime
Name Size Digest
cp311-macosx_arm64-accelerate Expired
5.03 MB
sha256:9df8909051d53a4a1994b5231da7cbd33953849fc026f055354f5b183ddf4123
cp311-macosx_x86_64-accelerate Expired
6.49 MB
sha256:db022beb59017bc6f03656860cedc09ff07b907a07918eea84e37d1708db3007
cp311-macosx_x86_64-openblas Expired
19.9 MB
sha256:7894c769f94a1d6d7ff640caaff10549c0c11999d7fb4465eadd0beffbfe4be8
cp311-manylinux_aarch64- Expired
13.7 MB
sha256:a9327781fe99417b5c888681af7b61272a6db640076289529715513d86096fa6
cp311-manylinux_x86_64- Expired
16 MB
sha256:0d6f5901c6a1771900424137de9297b24af4d1978ef34d668f5365c4584966e5
cp311-musllinux_aarch64- Expired
15 MB
sha256:fd3401a94fe4b67857b9947ded2977efc02482e8b24b386b28c84cb472383d97
cp311-musllinux_x86_64- Expired
17.6 MB
sha256:eaa2f9bdf0e50f628c50ff44af3a2291259ec384b4d30f3bf009dc759829d47d
cp311-win32- Expired
6.2 MB
sha256:be82703778d3d60972d3bdf63cb20c54042114aaa0ca685754601ecdb9da02e7
cp311-win_amd64- Expired
12.3 MB
sha256:908373620caeec1821e484f8adef0bc32a48de202def17d0c00c64d1f1937f56
cp311-win_arm64- Expired
9.86 MB
sha256:bb02dc2fe0e31d13ba4e5088abce663da791b1fe6c60813b0bb714fd18dedc50
sdist Expired
19.5 MB
sha256:2c45fe3b680ab57fff27c1940d719587b97fdc491a6e523abe16bd259254a882