Skip to content

SEP: Namespaces using URIs #2364

SEP: Namespaces using URIs

SEP: Namespaces using URIs #2364

Triggered via pull request August 3, 2025 07:41
Status Success
Total duration 2m 47s
Artifacts

pull-request-checks.yml

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

Annotations

16 warnings and 4 notices
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>01xKPaAAAAACd8dqZqdKaTLrumYBDQ4NQQkwyQUEyMDMwMTA5MDE3AEVkZ2U=
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>01xKPaAAAAAD0YFOXAI3/Q6qHsIdXsnwZQ0hHRURHRTE5MTYARWRnZQ==
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>02RKPaAAAAAB1sKqkgmscRpvh2jLZ3rBfQkwyQUEyMDMwMTA5MDQ3AEVkZ2U=
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>02hKPaAAAAAAVFLD2YbZtR4JnYSxNR0uwQlkzRURHRTAyMDgARWRnZQ==
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>0FxOPaAAAAACtKbPRkmQ8T7ntULXU/cqdQkwyQUEyMDMwMTA5MDM1AEVkZ2U=
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>0JBOPaAAAAACmwnTJ1SYFQITd8VHj8DyjQkwyQUEyMDMwMTA2MDA3AEVkZ2U=
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>0JBOPaAAAAAAX3Uih+Ek+R7lYLrdStJSLUEFPRURHRTA1MTYARWRnZQ==
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>0PhOPaAAAAAAoKaQwLydLT5pzIAU0EYGNQkwyQUEyMDMwMTA2MDM3AEVkZ2U=
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