Skip to content

Tests

Tests #196

Triggered via schedule September 15, 2025 09:02
Status Success
Total duration 16m 48s
Artifacts

test.yaml

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

Annotations

40 warnings and 3 notices
3.11, ubuntu-latest
powershell is not supported
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>02dfHaAAAAAB5BQJkdazaQ4CR1FPlADSmRE0yRURHRTA3MDcARWRnZQ==
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>0btbHaAAAAADAVZRMfnh+RJZPuQs18sfiRE0yRURHRTA3MDcARWRnZQ==
3.11, ubuntu-latest
Failed to restore: Cache service responded with 400
3.11, ubuntu-latest
Failed to restore: Cache service responded with 400
3.10, ubuntu-latest
powershell is not supported
3.10, 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>09NfHaAAAAAAQLRlMY4xnRaRUjKYd6BArQ0hJMzBFREdFMDIxNABFZGdl
3.10, 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>0etbHaAAAAACoJ6bc54vDQoHQPkzRNtL4Q0hJMzBFREdFMDIxNABFZGdl
3.10, ubuntu-latest
Failed to restore: Cache service responded with 400
3.10, ubuntu-latest
Failed to restore: Cache service responded with 400
3.11, macos-latest
powershell is not supported
3.11, 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>0IdjHaAAAAACblMcsRclxQ6rlMUjnGtUWQlkzRURHRTA0MDkARWRnZQ==
3.11, 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>0y9bHaAAAAAAZanw7yTXkRJmutiwzdz10UEFPRURHRTA1MDkARWRnZQ==
3.11, macos-latest
Failed to restore: Cache service responded with 400
3.11, macos-latest
Failed to restore: Cache service responded with 400
3.12, macos-latest
powershell is not supported
3.12, 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>0LdjHaAAAAADPhmyHoHP9Sotaf1WOIp0oUEFPRURHRTA1MTUARWRnZQ==
3.12, 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>0utbHaAAAAACXh3Cronh5SIQZP6zp/0MYQlkzRURHRTA1MTgARWRnZQ==
3.12, macos-latest
Failed to restore: Cache service responded with 400
3.12, macos-latest
Failed to restore: Cache service responded with 400
3.10, macos-latest
powershell is not supported
3.10, 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>0QNjHaAAAAADsh3VzKaXwS5tJiza+HJqvUEFPRURHRTA1MTEARWRnZQ==
3.10, 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>04tbHaAAAAACSe9ZLTmqWTZIMz97IIGKmUEFPRURHRTA1MTkARWRnZQ==
3.10, macos-latest
Failed to restore: Cache service responded with 400
3.10, macos-latest
Failed to restore: Cache service responded with 400
3.10, windows-latest
powershell is not supported
3.10, 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>0idnHaAAAAACUESNpHJS7T5agb3hkEIt6QkwyQUEyMDMwMTA2MDIxAEVkZ2U=
3.10, 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>0RNfHaAAAAABPKb+47CanQKmxx/JjE+LBQkwyQUEyMDMwMTA2MDIxAEVkZ2U=
3.10, windows-latest
Failed to restore: Cache service responded with 400
3.10, windows-latest
Failed to restore: Cache service responded with 400
3.12, windows-latest
powershell is not supported
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>02dnHaAAAAACWI/nwvb+lSKD9Rd6hQc/pQ0hJMzBFREdFMDMyMgBFZGdl
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>0j9fHaAAAAABsb+zj1/6vQJJ3SxbcaAK0Q0hJMzBFREdFMDMyMgBFZGdl
3.12, windows-latest
Failed to restore: Cache service responded with 400
3.12, windows-latest
Failed to restore: Cache service responded with 400
3.11, windows-latest
powershell is not supported
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>0ANrHaAAAAADKTle81LK6TbkGOVcj6jv3Q0hJMzBFREdFMDIxOQBFZGdl
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>0eNfHaAAAAAC3T4hNfbnPT4PU/lWOgz4SQ0hJMzBFREdFMDIxOQBFZGdl
3.11, windows-latest
Failed to restore: Cache service responded with 400
3.11, windows-latest
Failed to restore: Cache service responded with 400
3.10, 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
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
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