Skip to content

Fix workflow

Fix workflow #6

Triggered via push September 15, 2025 18:17
Status Success
Total duration 33s
Artifacts

test.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

24 warnings and 4 notices
test (ubuntu-latest, 3.11)
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>0JljIaAAAAACU9i+L7iJcRZMU9ERjHsSGQkwyQUEyMDMwMTA1MDQ5AEVkZ2U=
test (ubuntu-latest, 3.11)
Failed to restore: Cache service responded with 400
test (ubuntu-latest, 3.12)
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>0JljIaAAAAAAPlvHTuhHDQqajJ01CDLbzQkwyQUEyMDMwMTA5MDUzAEVkZ2U=
test (ubuntu-latest, 3.12)
Failed to restore: Cache service responded with 400
test (ubuntu-latest, 3.10)
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>0JljIaAAAAABhQuQ3CvC7SKgI+3Le+e9tQkwyQUEyMDMwMTA3MDI1AEVkZ2U=
test (ubuntu-latest, 3.10)
Failed to restore: Cache service responded with 400
test (ubuntu-latest, 3.13)
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>0J1jIaAAAAADaYApgpNrSRIov0YhZO3O2Q0hJMzBFREdFMDMwNwBFZGdl
test (ubuntu-latest, 3.13)
Failed to restore: Cache service responded with 400
test (macos-latest, 3.11)
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>0KljIaAAAAACgiso7IO8OS70s7pu3h/0rU04xRURHRTIxMTMARWRnZQ==
test (macos-latest, 3.11)
Failed to restore: Cache service responded with 400
test (macos-latest, 3.12)
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>0K1jIaAAAAADNqWdDIilSQ7A6IiAw0NfSUEFPRURHRTA1MTIARWRnZQ==
test (macos-latest, 3.12)
Failed to restore: Cache service responded with 400
test (macos-latest, 3.13)
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>0LljIaAAAAAD3BpHiZMORTr20lxGpvRmZQkwyQUEyMDMwMTA5MDE3AEVkZ2U=
test (macos-latest, 3.13)
Failed to restore: Cache service responded with 400
test (windows-latest, 3.12)
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>0M1jIaAAAAABho7beKlhtRJ4TeRWNyizvQkwyQUEyMDMwMTA2MDA3AEVkZ2U=
test (windows-latest, 3.12)
Failed to restore: Cache service responded with 400
test (windows-latest, 3.10)
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>0NFjIaAAAAAAFRElcUr/1QJFP2fUQqVO2QkwyQUEyMDMwMTA1MDI3AEVkZ2U=
test (windows-latest, 3.10)
Failed to restore: Cache service responded with 400
test (macos-latest, 3.10)
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>0NljIaAAAAAD5h1J72h06QIPIL8yOZQdGQkwyQUEyMDMwMTA3MDM5AEVkZ2U=
test (macos-latest, 3.10)
Failed to restore: Cache service responded with 400
test (windows-latest, 3.13)
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>0N1jIaAAAAABqO9k/+PjtRZW1kc1h+axxQkwyQUEyMDMwMTA5MDA3AEVkZ2U=
test (windows-latest, 3.13)
Failed to restore: Cache service responded with 400
test (windows-latest, 3.11)
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>0OVjIaAAAAACA6YgrdcxhQK2CRCxUH1ISQlkzRURHRTAxMTcARWRnZQ==
test (windows-latest, 3.11)
Failed to restore: Cache service responded with 400
test (windows-latest, 3.12)
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 (windows-latest, 3.10)
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 (windows-latest, 3.13)
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 (windows-latest, 3.11)
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