Skip to content

Implementation of SEP 973 - Additional metadata + icons support #2654

Implementation of SEP 973 - Additional metadata + icons support

Implementation of SEP 973 - Additional metadata + icons support #2654

Triggered via pull request September 9, 2025 21:23
Status Failure
Total duration 4m 4s
Artifacts

pull-request-checks.yml

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

Annotations

1 error, 32 warnings, and 8 notices
checks / pre-commit
Process completed with exit code 1.
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>06prAaAAAAABhT3aBzBp1RqtmzX9/b9uEQkwyQUEyMDMwMTA2MDMxAEVkZ2U=
checks / test (3.10, 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>06prAaAAAAADtTwmUO+CES7PPrT+iRpkgQkwyQUEyMDMwMTA5MDA1AEVkZ2U=
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>065rAaAAAAADmvx+3tzg5Tb+IXmLRUOG4QkwyQUEyMDMwMTA1MDIxAEVkZ2U=
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>065rAaAAAAAAPBs/FqpIDSrQcB41qiiHJUEhYMzFFREdFMDIxMABFZGdl
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>07JrAaAAAAADw0kxQaCpST7kPz/c6jckJQ0hJMzBFREdFMDQxNQBFZGdl
checks / test (3.11, lowest-direct, 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>065rAaAAAAABmPQG9kJQCQKBtG30lAIadUEFPRURHRTA1MDgARWRnZQ==
checks / test (3.11, highest, 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>07JrAaAAAAAA5KDnKAttrS6RIz3WLCN5CQ0hJMzBFREdFMDQxMQBFZGdl
checks / test (3.10, highest, 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>07ZrAaAAAAABL1IIiklm3TbXnFPd0JVF5Q0hJMzBFREdFMDExOABFZGdl
checks / test (3.13, highest, ubuntu-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>0GZvAaAAAAABkbJDdy9jVTKwOT7b1hZDrRE0yRURHRTA4MTEARWRnZQ==
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>0GpvAaAAAAAC1TYza22bXRp0QWuKXu1D6UEhYMzFFREdFMDUxOQBFZGdl
checks / test (3.13, lowest-direct, windows-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>0HpvAaAAAAAA+eAcLswOYRr+gA4+iWzcQRE0yRURHRTEwMTAARWRnZQ==
checks / test (3.10, lowest-direct, 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>0IJvAaAAAAABekRiDWOScQ7qU2nVBdaCHREVOMzAxMDAwMTA4MDIzAEVkZ2U=
checks / test (3.13, 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>0K5vAaAAAAADwGhkhQ8Y0TrHxnGP2nXVVRE0yRURHRTA3MTEARWRnZQ==
checks / test (3.11, 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>0PJvAaAAAAACQVnpp4HK0TbARZkBXLkBEQkwyQUEyMDMwMTA2MDE5AEVkZ2U=
checks / test (3.10, highest, 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>0a5vAaAAAAAAmdOw02PJVSKPLiAntdiBZUEFPRURHRTA2MTIARWRnZQ==
checks / test (3.12, 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>0uJvAaAAAAACQllF9CVnuRoEKqDwYhWdjQkwyQUEyMDMwMTA5MDAzAEVkZ2U=
checks / test (3.11, highest, windows-latest)
Failed to restore: Cache service responded with 400
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.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.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
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.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.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.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