Skip to content

Nightly Build (by @tomarnepedersen) #675

Nightly Build (by @tomarnepedersen)

Nightly Build (by @tomarnepedersen) #675

Triggered via schedule September 29, 2025 05:36
Status Success
Total duration 1m 48s
Artifacts 1

nightly_build.yml

on: schedule
Matrix: test / test
Matrix: test_future / test313
build_package  /  Build source distribution
11s
build_package / Build source distribution
build_and_publish_documentation  /  Build and publish documentation
29s
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.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/xraaAAAAADSN1FSi+3SQJAIkzjC+NG7Q0hJMzBFREdFMDIyMQBFZGdl
test / Test on 3.12-ubuntu-latest
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>0BhvaaAAAAABTuUMKDX4bTpeJo29hO7XWRE0yRURHRTA1MDcARWRnZQ==
test / Test on 3.11-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>0EhvaaAAAAADlsqWavschSbYavSK2V+QXUEhMMzBFREdFMDExNgBFZGdl
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>0IRvaaAAAAAAPcfoGULUOToMtlYV3dHo4UEFPRURHRTA1MTAARWRnZQ==
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>0MRvaaAAAAADeYH47ahufQ4AwDthGDV2ZRE0yRURHRTAxMDkARWRnZQ==
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>0URvaaAAAAACzW4861MjlQrYPwrT13wgsREVOMzAxMDAwMTAxMDE3AEVkZ2U=
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:b1d9712141a9000cdf63446964d5e957e01fb07db379735e4ff48116959667d1