Create wheels_test_313.yml #1
IvanIsCodingwheels_test_313.yml
on: push
Publish rustworkx-core
13s
Matrix: build_wheels_aarch64
Matrix: build_wheels_musl_aarch64
Matrix: build_wheels_ppc64le
Matrix: build_wheels_s390x
Annotations
6 errors and 13 warnings
|
Publish rustworkx-core
Process completed with exit code 101.
|
|
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:IvanIsCoding/rustworkx:environment:release`
* `repository`: `IvanIsCoding/rustworkx`
* `repository_owner`: `IvanIsCoding`
* `repository_owner_id`: `8753214`
* `job_workflow_ref`: `IvanIsCoding/rustworkx/.github/workflows/wheels_test_313.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
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:IvanIsCoding/rustworkx:environment:release`
* `repository`: `IvanIsCoding/rustworkx`
* `repository_owner`: `IvanIsCoding`
* `repository_owner_id`: `8753214`
* `job_workflow_ref`: `IvanIsCoding/rustworkx/.github/workflows/wheels_test_313.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
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:IvanIsCoding/rustworkx:environment:release`
* `repository`: `IvanIsCoding/rustworkx`
* `repository_owner`: `IvanIsCoding`
* `repository_owner_id`: `8753214`
* `job_workflow_ref`: `IvanIsCoding/rustworkx/.github/workflows/wheels_test_313.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
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:IvanIsCoding/rustworkx:environment:release`
* `repository`: `IvanIsCoding/rustworkx`
* `repository_owner`: `IvanIsCoding`
* `repository_owner_id`: `8753214`
* `job_workflow_ref`: `IvanIsCoding/rustworkx/.github/workflows/wheels_test_313.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Upload shared build wheels
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:IvanIsCoding/rustworkx:environment:release`
* `repository`: `IvanIsCoding/rustworkx`
* `repository_owner`: `IvanIsCoding`
* `repository_owner_id`: `8753214`
* `job_workflow_ref`: `IvanIsCoding/rustworkx/.github/workflows/wheels_test_313.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Build wheels on macos-14
Bumping MACOSX_DEPLOYMENT_TARGET (10.12) to the minimum required (11.0).
|
|
Build wheels on macos-14
pipx 1.7.1 is already installed and up-to-date.
To reinstall 1.7.1, run:
brew reinstall pipx
|
|
Build wheels on macos-14
Bumping MACOSX_DEPLOYMENT_TARGET (10.12) to the minimum required (11.0).
|
|
Build wheels on macos-14
Bumping MACOSX_DEPLOYMENT_TARGET (10.12) to the minimum required (11.0).
|
|
Build wheels on macos-14
Bumping MACOSX_DEPLOYMENT_TARGET (10.12) to the minimum required (11.0).
|
|
Build wheels on macos-14
Bumping MACOSX_DEPLOYMENT_TARGET (10.12) to the minimum required (11.0).
|
|
Build wheels on macos-13
pipx 1.7.1 is already installed and up-to-date.
To reinstall 1.7.1, run:
brew reinstall pipx
|
|
Build wheels on macos-13
Bumping MACOSX_DEPLOYMENT_TARGET (10.12) to the minimum required (10.13).
|
|
Build wheels on macos-13
Bumping MACOSX_DEPLOYMENT_TARGET (10.12) to the minimum required (10.13).
|
|
Build wheels on ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-qemu-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build wheels on ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-qemu-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build wheels on ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-qemu-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build wheels on ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-qemu-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
shared-wheel-builds-macos-13
Expired
|
1.79 MB |
|
|
shared-wheel-builds-macos-14
Expired
|
1.63 MB |
|
|
shared-wheel-builds-ubuntu-latest
Expired
|
5.68 MB |
|
|
shared-wheel-builds-windows-latest
Expired
|
1.68 MB |
|
|
wheel-builds-aarch64
Expired
|
1.76 MB |
|
|
wheel-builds-musl-aarch64
Expired
|
1.8 MB |
|
|
wheel-builds-ppc64le
Expired
|
1.93 MB |
|
|
wheel-builds-s390x
Expired
|
3.12 MB |
|