Skip to content

MAINT: clean up PKG_CONFIG_PATH usage in cibw_before_build.sh #19

MAINT: clean up PKG_CONFIG_PATH usage in cibw_before_build.sh

MAINT: clean up PKG_CONFIG_PATH usage in cibw_before_build.sh #19

Triggered via push July 6, 2025 19:45
Status Failure
Total duration 11m 10s
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:36a1e7a0fa84424e0cc4ade1147c777af98fc0ea9e102477cd44833ff4aa57a3
cp311-macosx_x86_64-accelerate Expired
6.49 MB
sha256:9b8717883e052afb760d48172b764a8b179f348f138264e0b8e7875b30bdcf53
cp311-macosx_x86_64-openblas Expired
19.9 MB
sha256:acf861685dddd4bc9bd861730857f1fd6a30b690bf6aa22640e4c731c1f84f9c
cp311-manylinux_aarch64- Expired
13.7 MB
sha256:8207b4099f01fc4ab6fed4f9f96c097bce01291b0cad1f52795ffcc37d445195
cp311-manylinux_x86_64- Expired
16 MB
sha256:bf6741954ed22ed5033c319605601298da1cc320bb7404182b5e16b7b148c8cb
cp311-musllinux_aarch64- Expired
15 MB
sha256:721999a4f3efb2244b798a4455f122579b16c50bd7958fa5604038d717ab8ae3
cp311-musllinux_x86_64- Expired
17.6 MB
sha256:c51a379bc24d9f5a70c7c0efa84455023d4df7814d50d4e71365256ff028c67c
cp311-win32- Expired
6.2 MB
sha256:e772e491227eb5cc0cc130a39a7765d09795002c04648f6e90cb5ae186668349
cp311-win_amd64- Expired
12.3 MB
sha256:8aa234fb7edd8a04240a039f531eea5218cf154b2bdd626314b5df192cfaf382
cp311-win_arm64- Expired
9.86 MB
sha256:2d3b65a2e6fd7d8f67bf28bffa6cde2ad1c84ba3e82eaa86ec3aa1dbac1ca09a
sdist Expired
19.5 MB
sha256:de90140e317d51bcb28d3cbd50adab53e12f24af53594ad5e3c200b831f2b29c