Skip to content

Add test for ProtectedResourceMetadataParsing #2382

Add test for ProtectedResourceMetadataParsing

Add test for ProtectedResourceMetadataParsing #2382

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

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
16s
checks / pre-commit
checks  /  readme-snippets
13s
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.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>07tiRaAAAAAASxuf3D0gTRa2K9puQCQ1eQkwyQUEyMDMwMTA3MDAzAEVkZ2U=
checks / test (3.12, 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>079iRaAAAAADgQFYvBBkFSIoUcc5aj3zHQkwyQUEyMDMwMTA3MDIzAEVkZ2U=
checks / test (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>08NiRaAAAAADv+3FreblsRL8AqcxqnBy9Q0gxRURHRTE4MjAARWRnZQ==
checks / test (3.11, 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>08diRaAAAAAAy2Qgx+d1QR4bTRXACiZnAQlkzRURHRTA0MTkARWRnZQ==
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>0MtmRaAAAAADPGT9Kx3uBTYPOdPItOrSpQlkzRURHRTAzMTAARWRnZQ==
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>0OtmRaAAAAACeijz3iOPJTr5VUeMqmSAYQ0gxRURHRTE4MTAARWRnZQ==
checks / test (3.11, 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>0O9mRaAAAAACoLa9dcCvHQrKq4AjvmvzbUEhYMzFFREdFMDIxMQBFZGdl
checks / test (3.12, 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>0PtmRaAAAAADJTwvvBScmQLffo/ziK6SeUEFPRURHRTA2MTcARWRnZQ==
checks / test (3.13, 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.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
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