Use proper sync resolution in CI #2577
Kludexpull-request-checks.yml
on: pull_request
checks
/
pre-commit
30s
checks
/
readme-snippets
9s
Matrix: checks / test
Annotations
5 errors, 27 warnings, and 8 notices
|
checks / Test (3.12) (ubuntu-latest) (lowest-direct)
Process completed with exit code 1.
|
|
checks / Test (3.10) (windows-latest) (lowest-direct)
Process completed with exit code 1.
|
|
checks / Test (3.12) (windows-latest) (lowest-direct)
Process completed with exit code 1.
|
|
checks / Test (3.11) (windows-latest) (lowest-direct)
Process completed with exit code 1.
|
|
checks / Test (3.13) (windows-latest) (lowest-direct)
Process completed with exit code 1.
|
|
checks / Test (3.11) (ubuntu-latest) (lowest-direct)
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>0xGazaAAAAABOMOn8d/oeT4Z2yfxHzZN0Q0hJMzBFREdFMDEyMABFZGdl
|
|
checks / Test (3.11) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.12) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.12) (ubuntu-latest) (highest)
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>0w2azaAAAAADKaqWb9b6HRqsrux52r8JgUEhYMzFFREdFMDIyMQBFZGdl
|
|
checks / Test (3.12) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.13) (ubuntu-latest) (highest)
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>0xGazaAAAAABTAMH/7BERQqU2xhP9NBW6RE0yRURHRTA4MTYARWRnZQ==
|
|
checks / Test (3.13) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.10) (ubuntu-latest) (highest)
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>0xGazaAAAAADD/ihW1Q4pSa6kMURJxBj3RE0yRURHRTEwMTAARWRnZQ==
|
|
checks / Test (3.10) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.10) (ubuntu-latest) (lowest-direct)
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>0xWazaAAAAABI+UkqH3PXTYBF/+9WMd7zUEFPRURHRTA2MDkARWRnZQ==
|
|
checks / Test (3.10) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.11) (ubuntu-latest) (highest)
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>0xmazaAAAAACK+laVclNvSoqCWQSpDZ47UEhYMzFFREdFMDIwOABFZGdl
|
|
checks / Test (3.11) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.13) (ubuntu-latest) (lowest-direct)
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>0xWazaAAAAAD64F/+QgSoT5ME3TtI1F03QlkzRURHRTAxMTAARWRnZQ==
|
|
checks / Test (3.13) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.10) (windows-latest) (highest)
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>05GazaAAAAAA3twsAcUujQLd+VF2Tn9XhQ0hJMzBFREdFMDMxMABFZGdl
|
|
checks / Test (3.10) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.10) (windows-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.11) (windows-latest) (highest)
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>062azaAAAAABl2NrJHOkAT6jwzlDdsRQCQ0hJMzBFREdFMDIwOABFZGdl
|
|
checks / Test (3.11) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.12) (windows-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.12) (windows-latest) (highest)
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>07WazaAAAAADOQz6m5tEbRL1ALHoSvyFRUEFPRURHRTA1MTEARWRnZQ==
|
|
checks / Test (3.12) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.13) (windows-latest) (highest)
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>07WazaAAAAADUnGXZkaVBQZcc5rx7nl4yUEFPRURHRTA2MTgARWRnZQ==
|
|
checks / Test (3.13) (windows-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.11) (windows-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.13) (windows-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.10) (windows-latest) (highest)
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) (windows-latest) (lowest-direct)
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) (windows-latest) (highest)
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) (windows-latest) (lowest-direct)
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) (windows-latest) (highest)
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) (windows-latest) (highest)
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) (windows-latest) (lowest-direct)
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) (windows-latest) (lowest-direct)
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
|