Skip to content

Nightly Build (by @tomarnepedersen) #630

Nightly Build (by @tomarnepedersen)

Nightly Build (by @tomarnepedersen) #630

Triggered via schedule August 15, 2025 05:38
Status Success
Total duration 1m 41s
Artifacts 1

nightly_build.yml

on: schedule
Matrix: test / test
Matrix: test_future / test313
build_package  /  Build source distribution
10s
build_package / Build source distribution
build_and_publish_documentation  /  Build and publish documentation
30s
build_and_publish_documentation / Build and publish documentation
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 14 warnings, and 3 notices
test_future / Test on 3.13.0-alpha - 3.13.0-ubuntu-latest (experimental)
Process completed with exit code 2.
test_future / Test on 3.13.0-alpha - 3.13.0-windows-latest (experimental)
Process completed with exit code 1.
test_future / Test on 3.13.0-alpha - 3.13.0-ubuntu-latest (experimental)
Failed to restore: Cache service responded with 400
test / Test on 3.11-ubuntu-latest
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0+seeaAAAAAB9V1CGp3MFQb2ZkPx4yM6fRE0yRURHRTA5MjEARWRnZQ==
test / Test on 3.11-ubuntu-latest
Failed to restore: Cache service responded with 400
test / Test on 3.12-ubuntu-latest
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/ceeaAAAAAC8UrdRf5JBSoSxkVg0r2T+RE0yRURHRTA3MjEARWRnZQ==
test / Test on 3.12-ubuntu-latest
Failed to restore: Cache service responded with 400
test / Test on 3.11-windows-latest
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0DsieaAAAAABhqkpmgnQqSbIIUCjqC60KQkwyQUEyMDMwMTA4MDA3AEVkZ2U=
test / Test on 3.11-windows-latest
Failed to restore: Cache service responded with 400
test / Test on 3.12-windows-latest
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GMieaAAAAAB7O5IH4jqlS53osjL5do3wUEhYMzFFREdFMDUxNwBFZGdl
test / Test on 3.12-windows-latest
Failed to restore: Cache service responded with 400
build_package / Build source distribution
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0JsieaAAAAACupdRSQEzKQo/YVF01GSi2Q0hJMzBFREdFMDIwOABFZGdl
build_package / Build source distribution
Failed to restore: Cache service responded with 400
test_future / Test on 3.13.0-alpha - 3.13.0-windows-latest (experimental)
Failed to restore: Cache service responded with 400
build_and_publish_documentation / Build and publish documentation
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0RsieaAAAAACIBvVxwrxiRruB+G3MjUxYQ0hJMzBFREdFMDExNQBFZGdl
build_and_publish_documentation / Build and publish documentation
Failed to restore: Cache service responded with 400
test / Test on 3.11-windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test / Test on 3.12-windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
test_future / Test on 3.13.0-alpha - 3.13.0-windows-latest (experimental)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Artifacts

Produced during runtime
Name Size Digest
artifact Expired
96 KB
sha256:9e54ed1d91aeed6cc23adbfc3bc9c64c5ba7977539ccb595000e4350cde63b2f