Sometimes I wonder why I'm still using AI #7
Annotations
24 warnings and 4 notices
|
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>0rVjIaAAAAABxNSynKssWTrqCw4vVj3k4QkwyQUEyMDMwMTA3MDI1AEVkZ2U=
|
|
test (ubuntu-latest, 3.10)
Failed to restore: Cache service responded with 400
|
|
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>0r1jIaAAAAADLH9V1b7eHQ4MEZVx3jfnQQlkzRURHRTAxMTEARWRnZQ==
|
|
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>0sFjIaAAAAABuum0V2TSqQY3Krlz9KeltREVOMzAxMDAwMTAxMDE5AEVkZ2U=
|
|
test (ubuntu-latest, 3.12)
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>0sFjIaAAAAAA5EMqHzEJoR54haNNVXBYmQlkzRURHRTAzMTAARWRnZQ==
|
|
test (ubuntu-latest, 3.13)
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>0sljIaAAAAAAhqLCjoUHRTJyLQ1K32QiIU04xRURHRTIzMTMARWRnZQ==
|
|
test (macos-latest, 3.12)
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>0s1jIaAAAAADB20HliQOdRYqOErVDfaKqU04xRURHRTE1MjEARWRnZQ==
|
|
test (macos-latest, 3.11)
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>0tFjIaAAAAADW56fnV5RBQ5phhAOmCp7jU04xRURHRTE4MTYARWRnZQ==
|
|
test (macos-latest, 3.13)
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>0vljIaAAAAADUTMeijcWaSqe7IumCHZMyRE0yRURHRTA3MTgARWRnZQ==
|
|
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>0v1jIaAAAAADAh3pcsVBwRLSzp74H/ir/RE0yRURHRTA4MjIARWRnZQ==
|
|
test (windows-latest, 3.11)
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>0wVjIaAAAAADl71LkqvB0S5cUo1ftEHvzQkwyQUEyMDMwMTEwMDAzAEVkZ2U=
|
|
test (windows-latest, 3.12)
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>0xFjIaAAAAADEkooT1hyfQ5fDddsLD59hUEFPRURHRTA1MTMARWRnZQ==
|
|
test (macos-latest, 3.10)
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>0y1jIaAAAAACcrFL8ZSYrR7atVZefQDdqUEFPRURHRTA1MTgARWRnZQ==
|
|
test (windows-latest, 3.10)
Failed to restore: Cache service responded with 400
|
|
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
|
|
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
|