Skip to content
Pull request checks

GitHub Actions: Test on Python 3.14 #2611

Sign in to view logs

GitHub Actions: Test on Python 3.14

GitHub Actions: Test on Python 3.14 #2611

Triggered via pull request September 5, 2025 15:00
@cclausscclauss
synchronize #1346
cclauss:patch-2
Status Success
Total duration 1m 27s
Artifacts –

pull-request-checks.yml

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

Annotations

4 errors, 36 warnings, and 10 notices
checks / test (3.14rc2, highest, ubuntu-latest)
Process completed with exit code 2.
checks / test (3.14rc2, lowest-direct, ubuntu-latest)
Process completed with exit code 2.
checks / test (3.14rc2, highest, windows-latest)
Process completed with exit code 1.
checks / test (3.14rc2, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.14rc2, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.14rc2, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.14rc2, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.14rc2, lowest-direct, windows-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>0MPu6aAAAAACC/Q3G5bUbT6ogQ21lJW6ORE0yRURHRTA3MDcARWRnZQ==
checks / test (3.12, 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>0Mfu6aAAAAAAK8m82SMajQIb+n7KQwOpyQ0hJMzBFREdFMDIwOQBFZGdl
checks / test (3.11, 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>0Mfu6aAAAAADF5tXcw/TlTpFyGFd9OcJtQ0hJMzBFREdFMDMyMgBFZGdl
checks / test (3.13, lowest-direct, 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>0Mfu6aAAAAAD0R4tVA/pEQKqf0UM35voGQ0hJMzBFREdFMDIwNwBFZGdl
checks / test (3.10, highest, 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>0Mvu6aAAAAADA1HZwGqhHQLVX0RIFTEt/RE0yRURHRTEwMTIARWRnZQ==
checks / test (3.11, 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>0N/u6aAAAAADP7ihGSi8zQoF8d44DghtdQkwyQUEyMDMwMTA3MDIzAEVkZ2U=
checks / test (3.12, highest, 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>0Nvu6aAAAAABsxxKHZ+gFRqVThSkHwbOPUEFPRURHRTA2MTAARWRnZQ==
checks / test (3.10, lowest-direct, 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>0Ovu6aAAAAACwW6gIeuO5R7EE+RUiedL7RE0yRURHRTA3MjEARWRnZQ==
checks / test (3.13, 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>0V/u6aAAAAABOz/tuV7qXRryYd6j6LxeJQkwyQUEyMDMwMTA5MDQ3AEVkZ2U=
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>0WPu6aAAAAABIlSIhVoyLRZ9qiqWh3R4aUEFPRURHRTA1MTMARWRnZQ==
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>0Wvu6aAAAAAAzauKBJKg1SKG8D3y7X14EQkwyQUEyMDMwMTA2MDUxAEVkZ2U=
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>0Wvu6aAAAAACM7grUtpoxQqmZWRhMjKRlQkwyQUEyMDMwMTEwMDIzAEVkZ2U=
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 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>0W/u6aAAAAAA01HG8LycqT6UonWNF9ff0UEhYMzFFREdFMDYyMABFZGdl
checks / test (3.11, highest, 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>0W/u6aAAAAADf8cB9m+EhSLZkfdtR+tsJUEhYMzFFREdFMDUyMQBFZGdl
checks / test (3.10, highest, 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>0YPu6aAAAAAC1Z+wCidIUSaf0Kwyoc/UlRE0yRURHRTA4MjIARWRnZQ==
checks / test (3.12, lowest-direct, 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>0YPu6aAAAAADP8G/UO89yQLlzceOT0KQrUEhYMzFFREdFMDYxMQBFZGdl
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.14rc2, 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.14rc2, 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.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.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, 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, 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