fix: tool cache refresh with nested handler invocation #2535
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
31s
checks
/
readme-snippets
11s
Matrix: checks / test
Annotations
32 warnings and 8 notices
|
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>0PTCraAAAAAAUEusPfrQ+RpyY8lNGG14CQkwyQUEyMDMwMTA1MDE5AEVkZ2U=
|
|
checks / test (3.12, 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>0PTCraAAAAAC+FelaNLpaSZrytpNBux1cQkwyQUEyMDMwMTA5MDMzAEVkZ2U=
|
|
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 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>0PjCraAAAAABE1cM2oi+FQJKrVp8AMhugQkwyQUEyMDMwMTA4MDQ5AEVkZ2U=
|
|
checks / test (3.11, lowest-direct, 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>0PzCraAAAAABCTzrge/U3RrEH9+D7VOsZQkwyQUEyMDMwMTA2MDAzAEVkZ2U=
|
|
checks / test (3.13, lowest-direct, 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>0PzCraAAAAADQ5xypXW5aQ4ZOqwRWcRc8Q0gxRURHRTIxMDcARWRnZQ==
|
|
checks / test (3.13, 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>0PzCraAAAAADXwo9a7ys0S6HXWHNBIjPDRE0yRURHRTA5MjAARWRnZQ==
|
|
checks / test (3.11, highest, 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>0QDCraAAAAADsmp+S9jdlTaznCSdzS9crRE0yRURHRTA5MDcARWRnZQ==
|
|
checks / test (3.10, lowest-direct, 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>0QDCraAAAAAAoe+kGYhQtSoq+aVaOM1MdRE0yRURHRTA5MTUARWRnZQ==
|
|
checks / test (3.10, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, lowest-direct, 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>0XzCraAAAAADHEn6SndsuRJkewnN1l2eAQ0gxRURHRTE0MTEARWRnZQ==
|
|
checks / test (3.10, lowest-direct, 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>0YTCraAAAAAD0FndQk8IVQbw2tEtyXHr/QkwyQUEyMDMwMTA5MDM5AEVkZ2U=
|
|
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>0ZjCraAAAAABk1h70cVCJQ5V2GZe9W+veQ0hJMzBFREdFMDQxMwBFZGdl
|
|
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 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>0ZjCraAAAAADG0Sj3VYclQIgnLngWzOWoQ0hJMzBFREdFMDQyMABFZGdl
|
|
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 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>0ZzCraAAAAABzQeMnm6waRpkpa1/YwR2RQkwyQUEyMDMwMTA3MDQ3AEVkZ2U=
|
|
checks / test (3.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, lowest-direct, 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>0ZzCraAAAAACpM4gkrlAgR4fof0RfjZA6QlkzRURHRTAyMTgARWRnZQ==
|
|
checks / test (3.13, lowest-direct, windows-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>0aTCraAAAAAAYldvU8bv8SIG9OrGPF7hjRE0yRURHRTEwMTYARWRnZQ==
|
|
checks / test (3.12, highest, 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>0ajCraAAAAACPvLp96DJxTp5HQeTUOJXjRE0yRURHRTEwMDgARWRnZQ==
|
|
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
|
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.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.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, 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, 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
|