Skip to content

Add test for ProtectedResourceMetadataParsing #2381

Add test for ProtectedResourceMetadataParsing

Add test for ProtectedResourceMetadataParsing #2381

Triggered via pull request August 5, 2025 10:10
Status Failure
Total duration 2m 31s
Artifacts

pull-request-checks.yml

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

Annotations

1 error, 16 warnings, and 4 notices
checks / pre-commit
Process completed with exit code 1.
checks / test (3.11, 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>05tiRaAAAAAA+p/OMAEo0QoS+Ilfl3+3TQkwyQUEyMDMwMTA1MDAzAEVkZ2U=
checks / test (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, 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>059iRaAAAAADNV0jQJ4MGQbkGMiYZZMW4QkwyQUEyMDMwMTA1MDM1AEVkZ2U=
checks / test (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, 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>06NiRaAAAAADHIdQFTA3TTY5u3AjduVALUEFPRURHRTA1MjAARWRnZQ==
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, 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>069iRaAAAAABY6sqtM6iGRJyoROARJl1/UEhYMzFFREdFMDYwNwBFZGdl
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, 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>0KtmRaAAAAABXPfuawE7nQav60elwgoQDUEFPRURHRTA1MTMARWRnZQ==
checks / test (3.10, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, 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>0L9mRaAAAAAD9oXEknri4QqG4t/XEf5nCQ0gxRURHRTIxMTMARWRnZQ==
checks / test (3.11, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, 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>0NdmRaAAAAABRRNzSRxOiRq+wt0Snp3/iRE0yRURHRTA3MDkARWRnZQ==
checks / test (3.13, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, 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>0PNmRaAAAAADxT931TW3eRqIrT0cHSYJKUEFPRURHRTA1MTgARWRnZQ==
checks / test (3.12, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, 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, 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, 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, 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