Use proper sync resolution in CI #2592
dsp-antpull-request-checks.yml
on: pull_request
checks
/
pre-commit
31s
checks
/
readme-snippets
11s
Matrix: checks / test
Annotations
4 errors, 28 warnings, and 8 notices
|
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.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.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>0hN22aAAAAACdWUHHZFjFS5JU5XMqFr6GQkwyQUEyMDMwMTA4MDA3AEVkZ2U=
|
|
checks / Test (3.12) (ubuntu-latest) (highest)
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>0hN22aAAAAABZqdg3WUSDRpwwsnBJzallQkwyQUEyMDMwMTA3MDA5AEVkZ2U=
|
|
checks / Test (3.11) (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>0hd22aAAAAADhUAhHteeDQoGBr14DMMzQQkwyQUEyMDMwMTA4MDI3AEVkZ2U=
|
|
checks / Test (3.13) (ubuntu-latest) (highest)
Failed to restore: Cache service responded with 400
|
|
checks / Test (3.12) (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>0ht22aAAAAACk5jBPR8BQRaFQdyVH+zXfRE0yRURHRTA5MTMARWRnZQ==
|
|
checks / Test (3.12) (ubuntu-latest) (lowest-direct)
Failed to restore: Cache service responded with 400
|
|
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>0ht22aAAAAAB6mnpTGAI/RKg7pRp1Z2RDRE0yRURHRTA5MTMARWRnZQ==
|
|
checks / Test (3.11) (ubuntu-latest) (lowest-direct)
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>0ht22aAAAAADJwOAibWmRRqsYTWn4jVrmQlkzRURHRTAzMTAARWRnZQ==
|
|
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>0iN22aAAAAAAyhwmcRlV3ToAzIvcZG1MmRE0yRURHRTEwMTYARWRnZQ==
|
|
checks / Test (3.10) (ubuntu-latest) (lowest-direct)
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>0iN22aAAAAABy4M+g8W7JQagXf73P+eTDUEFPRURHRTA1MTkARWRnZQ==
|
|
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>0rN22aAAAAACf3Itir2OHTIn1l3HAdq2QUEhYMzFFREdFMDYyMQBFZGdl
|
|
checks / Test (3.10) (windows-latest) (highest)
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>0rd22aAAAAACCQs5uxRoWSrF8ah7UGw8hQkwyQUEyMDMwMTA5MDIxAEVkZ2U=
|
|
checks / Test (3.11) (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.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>0tN22aAAAAABovdRpDb2TT6BcPSqS2zuEQkwyQUEyMDMwMTA5MDM1AEVkZ2U=
|
|
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>0tN22aAAAAACHRpiD/6METZIFyN+XTvUbUEhYMzFFREdFMDYwNwBFZGdl
|
|
checks / Test (3.13) (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.12) (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.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.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
|
|
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.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.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
|