Skip to content

Nightly Build (by @tomarnepedersen) #619

Nightly Build (by @tomarnepedersen)

Nightly Build (by @tomarnepedersen) #619

Triggered via schedule August 4, 2025 05:45
Status Success
Total duration 1m 37s
Artifacts 1

nightly_build.yml

on: schedule
Matrix: test / test
Matrix: test_future / test313
build_package  /  Build source distribution
12s
build_package / Build source distribution
build_and_publish_documentation  /  Build and publish documentation
31s
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>0AkmQaAAAAADEmNwOR44nR6Lx1yXy2fULQ0hHRURHRTE3MTgARWRnZQ==
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>0B0mQaAAAAACqmw8kO1T9SpARfe6PUtElQkwyQUEyMDMwMTA5MDE5AEVkZ2U=
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>0F0mQaAAAAABy7bYd8/6lS6qYD7qqg1wUQ0gxRURHRTIwMjAARWRnZQ==
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>0GEmQaAAAAABdsWOi7l23SI3UGs+OK0/3Q0gxRURHRTExMTUARWRnZQ==
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>0J0mQaAAAAAAG063dBGBaTp2DTOTsQL5ZQkwyQUEyMDMwMTA2MDUzAEVkZ2U=
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>0SUmQaAAAAAAStYR5IOd8TaKnCTGeQlotQlkzRURHRTAyMjAARWRnZQ==
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:3e3c3ef6c458fe9cfd64b0e627d0f1a78eb563e5ecd5bbb9de06a62268d8ba55