Skip to content

Remove code coverage test #5

Remove code coverage test

Remove code coverage test #5

Triggered via push September 15, 2025 18:12
Status Success
Total duration 44s
Artifacts

test.yml

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

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>0IVfIaAAAAACFflF8Yh3lS75o/ZyfhOhhQ0hJMzBFREdFMDMxOABFZGdl
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>0IVfIaAAAAAA6FL1h3xy5T6U/Ayr1JySlREVOMzAxMDAwMTA3MDIzAEVkZ2U=
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>0IVfIaAAAAACR1hBJXtJHRaGzUtBk3wPRU04xRURHRTMwMTcARWRnZQ==
test (macos-latest, 3.12)
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>0IVfIaAAAAAAZPs7pSFNrTr60ABgw9tZ9Q0hJMzBFREdFMDExMABFZGdl
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>0I1fIaAAAAAAq99hZQKvaRYNT7iyRtx/SQ0hJMzBFREdFMDEwOABFZGdl
test (ubuntu-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>0JFfIaAAAAACNL89hUfHhRKkKrYQECNkrU04xRURHRTE2MTMARWRnZQ==
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>0JFfIaAAAAAANZM47nlKGQboIzH6iAjHPUEFPRURHRTA2MDgARWRnZQ==
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>0L1fIaAAAAADsOBiDRghUQ5mhdCcCxgrwRE0yRURHRTA4MDgARWRnZQ==
test (windows-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>0MVfIaAAAAADQ7BQEm/x1S72TiQmBsmTKQkwyQUEyMDMwMTA1MDQ3AEVkZ2U=
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>0MVfIaAAAAACje6KOaqdUTqP7/BHSv3boUEhYMzFFREdFMDUwOABFZGdl
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>0M1fIaAAAAAC5eSxYQFJMQqSrFqh0UXmrUEFPRURHRTA1MjEARWRnZQ==
test (macos-latest, 3.10)
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>0OlfIaAAAAADJqVGmzM+ZRZyNCGuQGP1XQkwyQUEyMDMwMTA2MDM5AEVkZ2U=
test (windows-latest, 3.11)
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.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.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