Skip to content

Add ValidationOptions for lenient output schema validation #2541

Add ValidationOptions for lenient output schema validation

Add ValidationOptions for lenient output schema validation #2541

Triggered via pull request August 26, 2025 08:42
Status Failure
Total duration 1m 34s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
15s
checks / pre-commit
checks  /  readme-snippets
14s
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.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>0snOtaAAAAAAxIICakjSwQJAV4b17RoxWQkwyQUEyMDMwMTA4MDMzAEVkZ2U=
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>0snOtaAAAAACxCqS0oJyUQrB3vQ7eZHG8QkwyQUEyMDMwMTA2MDUxAEVkZ2U=
checks / test (3.10, 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>0snOtaAAAAABxUE7K1iN7QIWK6Q00VmVLQkwyQUEyMDMwMTA4MDQ3AEVkZ2U=
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>0s3OtaAAAAAAzjVZzrLxMSaCQ/rcI3QByQkwyQUEyMDMwMTA4MDQ5AEVkZ2U=
checks / test (3.11, 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>0s3OtaAAAAABF61hNIbvGSYQ24DU/i2f/QkwyQUEyMDMwMTA2MDM5AEVkZ2U=
checks / test (3.13, 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>0tHOtaAAAAAC4SBEU3VsOTLddA2KzXpioQkwyQUEyMDMwMTEwMDA1AEVkZ2U=
checks / test (3.10, highest, 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>0tHOtaAAAAABHyoUujb+gSJ3YZ0HSBrA7RE0yRURHRTA4MjEARWRnZQ==
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>0v3OtaAAAAAA0TtMrclJ4QZm6LQDngm1KQlkzRURHRTA1MjAARWRnZQ==
checks / test (3.12, highest, ubuntu-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>02nOtaAAAAADLqvw/oEvrT4thyQyIUj8dQkwyQUEyMDMwMTA2MDA5AEVkZ2U=
checks / test (3.13, 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>02XOtaAAAAADYv3ZoQSzQQYya+6pguLCJRE0yRURHRTA3MTcARWRnZQ==
checks / test (3.10, highest, 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>023OtaAAAAABO7ZIG30wDSJiU3YnFCHsxUEhYMzFFREdFMDUxNQBFZGdl
checks / test (3.10, lowest-direct, windows-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>03XOtaAAAAAAmE8aNdhoPTqbnVPssBmx9Q0hHRURHRTE5MTQARWRnZQ==
checks / test (3.12, 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>03XOtaAAAAADndeFrVPNeRLZyyv/KK+oAQkwyQUEyMDMwMTA1MDIzAEVkZ2U=
checks / test (3.13, 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>05HOtaAAAAADUQ/wDuZLRT573EPZ1z229UEFPRURHRTA1MTIARWRnZQ==
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>05XOtaAAAAAC6ytNmWpU2RYJg3Y44AdPKQlkzRURHRTAyMTcARWRnZQ==
checks / test (3.11, 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>063OtaAAAAACpSMI7zWS2T64KKD5VNoQYQkwyQUEyMDMwMTEwMDM5AEVkZ2U=
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
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, 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.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.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, 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
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