Skip to content
Wheel Builds

Publish aarch64 musl with trusted publishers #135

Sign in to view logs

Publish aarch64 musl with trusted publishers

Publish aarch64 musl with trusted publishers #135

Triggered via push October 17, 2023 02:01
@IvanIsCodingIvanIsCoding
pushed f5be273
musl-aarch64
Status Failure
Total duration 53m 34s
Artifacts 1

wheels.yml

on: push
Matrix: build_wheels310
Matrix: build_wheels311
Matrix: build_wheels312
Matrix: build_wheels37
Matrix: build_wheels38
Matrix: build_wheels39
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 6 notices
Build wheels on ubuntu-latest
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) 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:Qiskit/rustworkx:ref:refs/heads/musl-aarch64` * `repository`: `Qiskit/rustworkx` * `repository_owner`: `Qiskit` * `repository_owner_id`: `30696987` * `job_workflow_ref`: `Qiskit/rustworkx/.github/workflows/wheels.yml@refs/heads/musl-aarch64` * `ref`: `refs/heads/musl-aarch64`
Build wheels on ubuntu-latest
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) 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:Qiskit/rustworkx:ref:refs/heads/musl-aarch64` * `repository`: `Qiskit/rustworkx` * `repository_owner`: `Qiskit` * `repository_owner_id`: `30696987` * `job_workflow_ref`: `Qiskit/rustworkx/.github/workflows/wheels.yml@refs/heads/musl-aarch64` * `ref`: `refs/heads/musl-aarch64`
Build wheels on ubuntu-latest
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) 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:Qiskit/rustworkx:ref:refs/heads/musl-aarch64` * `repository`: `Qiskit/rustworkx` * `repository_owner`: `Qiskit` * `repository_owner_id`: `30696987` * `job_workflow_ref`: `Qiskit/rustworkx/.github/workflows/wheels.yml@refs/heads/musl-aarch64` * `ref`: `refs/heads/musl-aarch64`
Build wheels on ubuntu-latest
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) 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:Qiskit/rustworkx:ref:refs/heads/musl-aarch64` * `repository`: `Qiskit/rustworkx` * `repository_owner`: `Qiskit` * `repository_owner_id`: `30696987` * `job_workflow_ref`: `Qiskit/rustworkx/.github/workflows/wheels.yml@refs/heads/musl-aarch64` * `ref`: `refs/heads/musl-aarch64`
Build wheels on ubuntu-latest
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) 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:Qiskit/rustworkx:ref:refs/heads/musl-aarch64` * `repository`: `Qiskit/rustworkx` * `repository_owner`: `Qiskit` * `repository_owner_id`: `30696987` * `job_workflow_ref`: `Qiskit/rustworkx/.github/workflows/wheels.yml@refs/heads/musl-aarch64` * `ref`: `refs/heads/musl-aarch64`
Build wheels on ubuntu-latest
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) 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:Qiskit/rustworkx:ref:refs/heads/musl-aarch64` * `repository`: `Qiskit/rustworkx` * `repository_owner`: `Qiskit` * `repository_owner_id`: `30696987` * `job_workflow_ref`: `Qiskit/rustworkx/.github/workflows/wheels.yml@refs/heads/musl-aarch64` * `ref`: `refs/heads/musl-aarch64`
Build wheels on ubuntu-latest
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field
Build wheels on ubuntu-latest
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field
Build wheels on ubuntu-latest
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field
Build wheels on ubuntu-latest
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field
Build wheels on ubuntu-latest
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field
Build wheels on ubuntu-latest
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field

Artifacts

Produced during runtime
Name Size
artifact Expired
11.4 MB