Skip to content

Add readme for release. #1

Add readme for release.

Add readme for release. #1

Triggered via push September 4, 2024 12:32
Status Failure
Total duration 1m 14s
Artifacts 1

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Publish Python distribution 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 (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:DCGM/lm-evaluation-harness:environment:pypi` * `repository`: `DCGM/lm-evaluation-harness` * `repository_owner`: `DCGM` * `repository_owner_id`: `7933191` * `job_workflow_ref`: `DCGM/lm-evaluation-harness/.github/workflows/publish.yml@refs/tags/v0.1` * `ref`: `refs/tags/v0.1` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Publish Python distribution 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 (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:DCGM/lm-evaluation-harness:environment:testpypi` * `repository`: `DCGM/lm-evaluation-harness` * `repository_owner`: `DCGM` * `repository_owner_id`: `7933191` * `job_workflow_ref`: `DCGM/lm-evaluation-harness/.github/workflows/publish.yml@refs/tags/v0.1` * `ref`: `refs/tags/v0.1` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Build distribution
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Publish Python distribution to PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Publish Python distribution to TestPyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "python-package-distributions". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
python-package-distributions Expired
2.4 MB