SEP: Namespaces using URIs #2363
chughtapanpull-request-checks.yml
on: pull_request
checks
/
pre-commit
27s
checks
/
readme-snippets
10s
Matrix: checks / test
Annotations
16 warnings and 4 notices
|
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>0u6WOaAAAAAC/TLvx83ISRaqr5zjfOFMZQkwyQUEyMDMwMTA1MDMzAEVkZ2U=
|
|
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>0vKWOaAAAAAC3iCrtTW/oRZgeHVVd0YCOQkwyQUEyMDMwMTA4MDM3AEVkZ2U=
|
|
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
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>0vqWOaAAAAABmaGMXl6m7T4XK9DX78CnZUEhYMzFFREdFMDUxOABFZGdl
|
|
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>0vqWOaAAAAABgIm9CGoM/RohT9ZMdY0DWRE0yRURHRTA1MTUARWRnZQ==
|
|
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>0+aWOaAAAAADzBu3sCpqoSbnzlmdQ0k7aQ0hJMzBFREdFMDExMQBFZGdl
|
|
checks / test (3.10, 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>0BqaOaAAAAABAx95SkERCTYrvmwtqvAL4QkwyQUEyMDMwMTEwMDQ5AEVkZ2U=
|
|
checks / test (3.12, 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>0BqaOaAAAAACxymkxI8pER5jcOhW8OX7gUEhYMzFFREdFMDUwOABFZGdl
|
|
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>0C6aOaAAAAADMAA7J3i7HSIRcjT4KqRXIQkwyQUEyMDMwMTA1MDE3AEVkZ2U=
|
|
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.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.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
|