Skip to content

Nightly Cron

Nightly Cron #7

Triggered via schedule September 11, 2025 05:16
Status Failure
Total duration 26m 20s
Artifacts

cron.yml

on: schedule
Publish latest website  /  build-website
1m 15s
Publish latest website / build-website
deploy-test-pypi
1m 58s
deploy-test-pypi
Matrix: Tests with latest BoTorch & full dependencies / tests-and-coverage
Matrix: Tests with latest BoTorch & minimal dependencies / tests-and-coverage
Publish latest website  /  deploy-website
Publish latest website / deploy-website
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Publish latest website / build-website
Process completed with exit code 128.
deploy-test-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:mpolson64/Ax:ref:refs/heads/main` * `repository`: `mpolson64/Ax` * `repository_owner`: `mpolson64` * `repository_owner_id`: `10412352` * `workflow_ref`: `mpolson64/Ax/.github/workflows/cron.yml@refs/heads/main` * `job_workflow_ref`: `mpolson64/Ax/.github/workflows/cron.yml@refs/heads/main` * `ref`: `refs/heads/main` * `environment`: `MISSING` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Tests with latest BoTorch & full dependencies / tests-and-coverage (3.10)
Process completed with exit code 1.
Tests with latest BoTorch & full dependencies / tests-and-coverage (3.12)
Process completed with exit code 1.