Skip to content

Remove experiment.fetch_trial_data from the Dev API tutorial (#3337) #1735

Remove experiment.fetch_trial_data from the Dev API tutorial (#3337)

Remove experiment.fetch_trial_data from the Dev API tutorial (#3337) #1735

Triggered via push February 10, 2025 16:57
Status Failure
Total duration 2h 13m 7s
Artifacts 1

cron.yml

on: push
Publish latest website  /  build-website
2h 12m
Publish latest website / build-website
deploy-test-pypi
2m 38s
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
10s
Publish latest website / deploy-website
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 9 warnings
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.
Tests with latest BoTorch & minimal dependencies / tests-and-coverage (3.10)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Tests with latest BoTorch & minimal dependencies / tests-and-coverage (3.10)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-3.12.3-02dbef43400c41ffc7d3e51c3dd9650a07fbd5ca9ae28421f34fc36e47ec2f27
Tests with latest BoTorch & minimal dependencies / tests-and-coverage (3.12)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-3.12.3-02dbef43400c41ffc7d3e51c3dd9650a07fbd5ca9ae28421f34fc36e47ec2f27
Tests with latest BoTorch & minimal dependencies / tests-and-coverage (3.12)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Tests with latest BoTorch & full dependencies / tests-and-coverage (3.10)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-3.12.3-02dbef43400c41ffc7d3e51c3dd9650a07fbd5ca9ae28421f34fc36e47ec2f27
Tests with latest BoTorch & full dependencies / tests-and-coverage (3.12)
Cache not found for keys: setup-uv-1-x86_64-unknown-linux-gnu-3.12.3-02dbef43400c41ffc7d3e51c3dd9650a07fbd5ca9ae28421f34fc36e47ec2f27

Artifacts

Produced during runtime
Name Size
github-pages Expired
9.21 MB