Skip to content

CI

CI #832

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

ci.yml

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

Annotations

3 errors, 20 warnings, and 3 notices
build (ubuntu-latest)
Process completed with exit code 1.
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>0RLXQaAAAAABjpLUVdA3NSJXp0DMMtLKFQkwyQUEyMDMwMTEwMDIxAEVkZ2U=
lint
Failed to restore: Cache service responded with 400
build (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>0RLXQaAAAAABiR77ymG/IQYnllgEAxBKAQkwyQUEyMDMwMTA5MDMxAEVkZ2U=
build (ubuntu-latest)
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>0RrXQaAAAAACJL37ZJgbfRZkERSPt+1pIQkwyQUEyMDMwMTA5MDA5AEVkZ2U=
build (ubuntu-latest, 0.15.1)
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>0V7XQaAAAAABMEbglu4NXSbW3MOClkxEIQkwyQUEyMDMwMTEwMDE5AEVkZ2U=
build (macos-latest)
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>0RbXQaAAAAACKv7mrzSqmQ5L/9bO2xAF7REVOMzAxMDAwMTAyMDQ5AEVkZ2U=
build (ubuntu-latest, 0.14.0)
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>0UbXQaAAAAAAHMr1j5/PUSpIeB5pbxgurU04xRURHRTIyMTUARWRnZQ==
build (macos-latest, 0.14.0)
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>0XrXQaAAAAACrHXN0y47FTbeazpd58fiIU04xRURHRTI4MTQARWRnZQ==
build (macos-latest, 0.15.1)
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>0abXQaAAAAABaVTX5bjCOS6rD5tW2Im28QkwyQUEyMDMwMTEwMDM1AEVkZ2U=
build (windows-latest, 0.14.0)
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>0fbXQaAAAAAA9ZyEajnsZRZn77xovymQ8Q0hJMzBFREdFMDMxMABFZGdl
build (windows-latest)
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>0gLXQaAAAAABKmWj4XCHdSoEl1Rw4dZiqQ0hJMzBFREdFMDExMgBFZGdl
build (windows-latest, 0.15.1)
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)
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