Skip to content

Add 100% clean coverage #2650

Add 100% clean coverage

Add 100% clean coverage #2650

Triggered via pull request September 9, 2025 14:18
Status Failure
Total duration 3m 35s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
28s
checks / pre-commit
checks  /  readme-snippets
11s
checks / readme-snippets
Matrix: checks / test
Fit to window
Zoom out
Zoom in

Annotations

5 errors, 28 warnings, and 8 notices
checks / pre-commit
Process completed with exit code 1.
checks / test (3.11, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.12, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.10, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.13, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.13, highest, 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>0hDfAaAAAAAAyNSuPm9F2Rp1ebjvW/ZaEQkwyQUEyMDMwMTA5MDMzAEVkZ2U=
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, lowest-direct, 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>0iDfAaAAAAABLBz8VTsnYSZxuAx3x1cR9QkwyQUEyMDMwMTA1MDMxAEVkZ2U=
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, highest, 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>0hzfAaAAAAAC60Z9VpmmiRpFraexXIJ45QkwyQUEyMDMwMTA3MDQ3AEVkZ2U=
checks / test (3.12, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, highest, 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>0hzfAaAAAAACLo9GNWG2UTosol4t5DV/GUEhYMzFFREdFMDYxNQBFZGdl
checks / test (3.10, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, lowest-direct, 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>0ijfAaAAAAACPSyEA1OOxRY4ePrm7bPoORE0yRURHRTA5MTgARWRnZQ==
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, lowest-direct, 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>0ijfAaAAAAADLpqlhLB3aSLFV3i67jgJYRE0yRURHRTA3MTEARWRnZQ==
checks / test (3.11, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, lowest-direct, 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>0izfAaAAAAADE7thcTVcCSL017acPozvCUEFPRURHRTA2MTUARWRnZQ==
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, highest, 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>0mTfAaAAAAADbccKox4iJQJO7XvyRBH1iRE0yRURHRTA3MTEARWRnZQ==
checks / test (3.11, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, highest, 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>02TfAaAAAAADfAN3DKzU+Q4vVaCEcvzi7QkwyQUEyMDMwMTA4MDI5AEVkZ2U=
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, highest, 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>02zfAaAAAAACKGY9NaIdrT75jx3XTW9suUEFPRURHRTA1MTkARWRnZQ==
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, highest, 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>06DfAaAAAAAC9Zc4ixuNaSKzwZZPJ4/3hQkwyQUEyMDMwMTA4MDE3AEVkZ2U=
checks / test (3.11, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, highest, 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>0FDjAaAAAAAAmf9yl0h48RLL107tMIY1GUEFPRURHRTA1MDcARWRnZQ==
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, highest, 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
checks / test (3.10, highest, 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
checks / test (3.11, highest, 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
checks / test (3.11, lowest-direct, 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
checks / test (3.12, lowest-direct, 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
checks / test (3.10, lowest-direct, 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
checks / test (3.13, lowest-direct, 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
checks / test (3.13, highest, 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