Skip to content

Nightly Cron

Nightly Cron #42

Triggered via schedule June 13, 2024 10:37
Status Failure
Total duration 1d 8h 51m 3s
Artifacts

nightly.yml

on: schedule
Matrix: Test & Coverage / tests-and-coverage-pip
Package and test deployment to test.pypi.org
1m 51s
Package and test deployment to test.pypi.org
Test conda build
0s
Test conda build
Run tutorials without smoke test on latest PyTorch  /  ...  /  Run tutorials
1h 22m
Run tutorials without smoke test on latest PyTorch / GPyTorch / Ax / Run tutorials
Publish latest website  /  Publish website
Publish latest website / Publish website
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Package and test deployment to test.pypi.org
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:lnhutnam/botorch:ref:refs/heads/main` * `repository`: `lnhutnam/botorch` * `repository_owner`: `lnhutnam` * `repository_owner_id`: `52648432` * `job_workflow_ref`: `lnhutnam/botorch/.github/workflows/nightly.yml@refs/heads/main` * `ref`: `refs/heads/main` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Test & Coverage / Tests and coverage (pip, Python 3.10, ubuntu-latest)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
Run tutorials without smoke test on latest PyTorch / GPyTorch / Ax / Run tutorials
Process completed with exit code 1.
Test conda build
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.