Skip to content

CI

CI #838

Triggered via schedule September 28, 2025 02:32
Status Failure
Total duration 2m 58s
Artifacts

ci.yml

on: schedule
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 18 warnings, and 3 notices
build (macos-latest)
Process completed with exit code 1.
build (windows-latest)
Process completed with exit code 1.
lint
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>0TJ7YaAAAAAD2JT/1FkFBT6qbjNn4f1ZNQ0hJMzBFREdFMDExOABFZGdl
lint
Failed to restore: Cache service responded with 400
build (ubuntu-latest, 0.15.1)
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>0S57YaAAAAACfP/hSf3eeQbGrJ9u8H527UEhMMzBFREdFMDExOABFZGdl
build (ubuntu-latest, 0.15.1)
Failed to restore: Cache service responded with 400
build (macos-latest, 0.15.1)
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>0V57YaAAAAAA92wrhaYfiQaPvEHcDlUr3U04xRURHRTE4MjEARWRnZQ==
build (macos-latest, 0.15.1)
Failed to restore: Cache service responded with 400
build (macos-latest, 0.14.0)
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>0Vp7YaAAAAADyOMAElFfMQoye5beDinP/U04xRURHRTMwMjAARWRnZQ==
build (macos-latest, 0.14.0)
Failed to restore: Cache service responded with 400
build (ubuntu-latest, 0.14.0)
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>0TZ7YaAAAAABarFs0irOOSo8309tdXnzqUEhYMzFFREdFMDUxMwBFZGdl
build (ubuntu-latest, 0.14.0)
Failed to restore: Cache service responded with 400
build (macos-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>0aZ7YaAAAAAAHuFYst5igSrMbahloBmI2UEFPRURHRTA1MjAARWRnZQ==
build (macos-latest)
Failed to restore: Cache service responded with 400
build (windows-latest, 0.14.0)
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>0ep7YaAAAAAAAhNKz0ABQSobqAu+Drh2+UEhMMzBFREdFMDExOQBFZGdl
build (windows-latest, 0.14.0)
Failed to restore: Cache service responded with 400
build (windows-latest, 0.15.1)
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>0hp7YaAAAAAA3bypL+j2uTYL4iT+ic37lQ0hJMzBFREdFMDQwNgBFZGdl
build (windows-latest, 0.15.1)
Failed to restore: Cache service responded with 400
build (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>0jp7YaAAAAABfPCRTdQQnQKTO1uGfhIm3UEhMMzBFREdFMDIyMgBFZGdl
build (windows-latest)
Failed to restore: Cache service responded with 400
build (windows-latest, 0.14.0)
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
build (windows-latest, 0.15.1)
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
build (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