Skip to content

Add test for ProtectedResourceMetadataParsing #2384

Add test for ProtectedResourceMetadataParsing

Add test for ProtectedResourceMetadataParsing #2384

Triggered via pull request August 5, 2025 13:15
Status Failure
Total duration 2m 37s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
18s
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>0LASSaAAAAAD74caVSylCSLLu7p4FxlGXUEhYMzFFREdFMDYxNwBFZGdl
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>0LASSaAAAAABoXUCMXKMdSaU6YcmIPK8gUEFPRURHRTA1MTgARWRnZQ==
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>0MgSSaAAAAAABnTf8GGJRSIiBtKT0pnOpQkwyQUEyMDMwMTA4MDI5AEVkZ2U=
checks / test (3.10, 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>0OASSaAAAAACGN2tMlXekS4dt0M0/GmgQQ0hJMzBFREdFMDExMQBFZGdl
checks / test (3.13, 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>0bwSSaAAAAAAECSv7PWMeTaMoYd4Ca7lZQkwyQUEyMDMwMTA5MDA5AEVkZ2U=
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>0fQSSaAAAAAAF5XatFf9XS6ZUosh+BluVQkwyQUEyMDMwMTA4MDE5AEVkZ2U=
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>0gASSaAAAAAA4CjJhE1JITrd3mr7r1xAQQkwyQUEyMDMwMTA2MDMxAEVkZ2U=
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>0hwSSaAAAAACx1dPX+V/ERYL2yr0r6IWNQkwyQUEyMDMwMTA5MDA3AEVkZ2U=
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