Add 100% clean coverage #2768
Triggered via pull request
September 28, 2025 23:48
Kludex
Status
Success
Total duration
3m 41s
Artifacts
–
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
38s
checks
/
readme-snippets
14s
Matrix: checks / test
Annotations
12 errors, 20 warnings, and 8 notices
|
checks / test (3.10, highest, 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.11, highest, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.11, lowest-direct, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.12, highest, 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.12, lowest-direct, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
|
|
checks / test (3.11, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
|
|
checks / test (3.10, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
|
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
|
|
checks / test (3.13, highest, windows-latest)
Process completed with exit code 1.
|
|
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>0lsnZaAAAAAADipegTrgWSptp7iJNnEBXUEhMMzBFREdFMDIxMABFZGdl
|
|
checks / test (3.12, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
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>0l8nZaAAAAACRlzyaOUQcSL3fJf2LHqbBUEhMMzBFREdFMDQxOABFZGdl
|
|
checks / test (3.13, 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>0msnZaAAAAADOVmpgnrOcSqGZdm/PiD/0UEFPRURHRTA2MTQARWRnZQ==
|
|
checks / test (3.10, highest, 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>0msnZaAAAAABsa0xzc+OXRI7t/S2xf1giUEFPRURHRTA1MDkARWRnZQ==
|
|
checks / test (3.11, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, highest, 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.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, highest, 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.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
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 restore: Cache service responded with 400
|
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
|
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.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.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, 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.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.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.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
|