Skip to content

Add test for ProtectedResourceMetadataParsing #2396

Add test for ProtectedResourceMetadataParsing

Add test for ProtectedResourceMetadataParsing #2396

Triggered via pull request August 6, 2025 10:18
Status Failure
Total duration 2m 27s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
18s
checks / pre-commit
checks  /  readme-snippets
10s
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>0JCyTaAAAAADsrgFTZ7odRKk9V2expUR2Q0hJMzBFREdFMDMyMABFZGdl
checks / test (3.12, 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>0JSyTaAAAAABwM4NB0XB0QphW0HmzlZxEUEFPRURHRTA1MjIARWRnZQ==
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>0KiyTaAAAAADJkhStftlDSKBFlbspt2NvQlkzRURHRTA0MTQARWRnZQ==
checks / test (3.13, 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>0MiyTaAAAAABKffPmJuG0RJJqV9Pq7s/xUEhYMzFFREdFMDYxNgBFZGdl
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>0bCyTaAAAAADPsiA7Zy6fRq7Xsos31nBeQ0hJMzBFREdFMDQxNgBFZGdl
checks / test (3.10, 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>0cCyTaAAAAABEqxN/k8/xSo5jGe1X2PzlQkwyQUEyMDMwMTA4MDQ1AEVkZ2U=
checks / test (3.13, 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>0cyyTaAAAAADNM5nR3wu1Qb3sSiyohxHQQkwyQUEyMDMwMTA3MDM5AEVkZ2U=
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>0dSyTaAAAAACWSIhdmMZcQ6Q1zZlWizLCQ0gxRURHRTEzMTEARWRnZQ==
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.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.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