Skip to content

Nightly Build (by @tomarnepedersen) #628

Nightly Build (by @tomarnepedersen)

Nightly Build (by @tomarnepedersen) #628

Triggered via schedule August 13, 2025 05:38
Status Success
Total duration 2m 7s
Artifacts 1

nightly_build.yml

on: schedule
Matrix: test / test
Matrix: test_future / test313
build_package  /  Build source distribution
41s
build_package / Build source distribution
build_and_publish_documentation  /  Build and publish documentation
27s
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>09CScaAAAAACPkxCg6/fpToHZlXQuBmrgRE0yRURHRTA3MTMARWRnZQ==
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>09yScaAAAAACuZY7+1CENT7k65+EuMJsRUEFPRURHRTA2MTUARWRnZQ==
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>0CiWcaAAAAADDFglnwu8sTYFtxdrfKHM1Q0gxRURHRTIwMTgARWRnZQ==
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>0DiWcaAAAAAC3TkrfgrdQQprvdcH576eAUEFPRURHRTA1MTEARWRnZQ==
test / Test on 3.12-windows-latest
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_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>0HiWcaAAAAAApF9ODUFPmRaIL3N/oHXONQ0gxRURHRTA4MTEARWRnZQ==
build_package / Build source distribution
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>0WCWcaAAAAACA+McP/kwHRIxKs2dPIpM9RE0yRURHRTEwMDcARWRnZQ==
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:de3280dadcf8d13d427eaebc828f2f6fbd6295c889dc3edc49532c9fb7f598c6