[backport 2.3.x] TST: run python-dev CI on 3.14-dev (#61950) #25753
Triggered via pull request
September 12, 2025 17:15
jorisvandenbossche
Status
Failure
Total duration
1h 19m 54s
Artifacts
1
unit-tests.yml
on: pull_request
Linux-32-bit
20m 45s
Linux-Musl
23m 49s
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Annotations
77 errors, 148 warnings, and 5 notices
|
Linux-32-bit
Process completed with exit code 1.
|
|
Numpy Dev-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Numpy Dev-ubuntu-22.04
Process completed with exit code 1.
|
|
Linux-Musl
Process completed with exit code 1.
|
|
Pyarrow Nightly-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Pyarrow Nightly-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.11-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.11-ubuntu-22.04
Process completed with exit code 1.
|
|
Locale: zh_CN-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Locale: zh_CN-ubuntu-22.04
Process completed with exit code 1.
|
|
Locale: it_IT-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Locale: it_IT-ubuntu-22.04
Process completed with exit code 1.
|
|
Minimum Versions-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Minimum Versions-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.12-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.12-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.10-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.10-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.9-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.9-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
Process completed with exit code 1.
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Process completed with exit code 1.
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Process completed with exit code 1.
|
|
python-dev (windows-latest)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
python-dev (windows-latest)
Process completed with exit code 1.
|
|
python-dev (ubuntu-22.04)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
python-dev (ubuntu-22.04)
Process completed with exit code 1.
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Process completed with exit code 1.
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
Process completed with exit code 1.
|
|
Future infer strings-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Future infer strings-ubuntu-22.04
Process completed with exit code 1.
|
|
macos-14 actions-312.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
macos-14 actions-312.yaml
Process completed with exit code 1.
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Process completed with exit code 1.
|
|
python-dev (macOS-14)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
python-dev (macOS-14)
Process completed with exit code 1.
|
|
windows-latest actions-39.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
windows-latest actions-39.yaml
Process completed with exit code 1.
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Process completed with exit code 1.
|
|
python-dev (macOS-13)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
python-dev (macOS-13)
Process completed with exit code 1.
|
|
macos-14 actions-310.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
macos-14 actions-310.yaml
Process completed with exit code 1.
|
|
windows-latest actions-310.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
windows-latest actions-310.yaml
Process completed with exit code 1.
|
|
windows-latest actions-312.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
windows-latest actions-312.yaml
Process completed with exit code 1.
|
|
macos-13 actions-39.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
macos-13 actions-39.yaml
Process completed with exit code 1.
|
|
windows-latest actions-311.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
windows-latest actions-311.yaml
Process completed with exit code 1.
|
|
macos-14 actions-311.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
macos-14 actions-311.yaml
Process completed with exit code 1.
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
Process completed with exit code 1.
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Process completed with exit code 1.
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Process completed with exit code 1.
|
|
macos-14 actions-39.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
macos-14 actions-39.yaml
Process completed with exit code 1.
|
|
macos-13 actions-312.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
macos-13 actions-312.yaml
Process completed with exit code 1.
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Process completed with exit code 1.
|
|
macos-13 actions-311.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
macos-13 actions-311.yaml
Process completed with exit code 1.
|
|
macos-13 actions-310.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
macos-13 actions-310.yaml
Process completed with exit code 1.
|
|
Downstream Compat-ubuntu-22.04
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>0wVbEaAAAAAAYFYOd0V1oQpIalv44cAhKQ0hJMzBFREdFMDIxNgBFZGdl
|
|
Downstream Compat-ubuntu-22.04
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>00FXEaAAAAAA/aS9BcEg/SqfjPG2YRhMSQ0hJMzBFREdFMDIxNgBFZGdl
|
|
Downstream Compat-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Downstream Compat-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Pypy-ubuntu-22.04
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>0WlfEaAAAAADYME3GVX8YQ6vDW9jEaNueREVOMzAxMDAwMTAxMDM1AEVkZ2U=
|
|
Pypy-ubuntu-22.04
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>0uFXEaAAAAAAKtcwGLQ8ITY/fj6Gxq1ukREVOMzAxMDAwMTAxMDM1AEVkZ2U=
|
|
Pypy-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Pypy-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Numpy Dev-ubuntu-22.04
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>0u1rEaAAAAAD/rn9oBGCnSqmmQeuwR/HrUEhYMzFFREdFMDUxMgBFZGdl
|
|
Numpy Dev-ubuntu-22.04
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>0rlXEaAAAAAAzO2m6/hhFTq4zd77R/XJ5UEhYMzFFREdFMDUxMgBFZGdl
|
|
Numpy Dev-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Numpy Dev-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Pyarrow Nightly-ubuntu-22.04
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>0VlvEaAAAAAC3xiNturSzTb3/s4TK6J7sUEFPRURHRTA1MjIARWRnZQ==
|
|
Pyarrow Nightly-ubuntu-22.04
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>0r1XEaAAAAABvZGAzL6Z0S7ygSG2Fm11kUEFPRURHRTA1MjIARWRnZQ==
|
|
Pyarrow Nightly-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Pyarrow Nightly-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
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>091vEaAAAAABU2qrBVexfRJmjb7zqzaOxQkwyQUEyMDMwMTA1MDE3AEVkZ2U=
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
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>061XEaAAAAADhgFlCKEbmRZ0cM1jpo/2PQkwyQUEyMDMwMTA1MDE3AEVkZ2U=
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.11-ubuntu-22.04
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>0BFzEaAAAAAA7yufKqxmwQ6Kc1a20hYk6Q0hJMzBFREdFMDQwOQBFZGdl
|
|
Copy-on-Write 3.11-ubuntu-22.04
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+lXEaAAAAACpNzBtJ3EoT4vVzMg2SZtEQ0hJMzBFREdFMDQwOQBFZGdl
|
|
Copy-on-Write 3.11-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.11-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Locale: zh_CN-ubuntu-22.04
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>0IlzEaAAAAAB7IR9OVhekTKl55Iegy0/HREVOMzAxMDAwMTAyMDQ3AEVkZ2U=
|
|
Locale: zh_CN-ubuntu-22.04
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/FXEaAAAAAAkjr6U0n01QK5bjaEbtVM0REVOMzAxMDAwMTAyMDQ3AEVkZ2U=
|
|
Locale: zh_CN-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Locale: zh_CN-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Locale: it_IT-ubuntu-22.04
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>0JlzEaAAAAACNZEGI49hkSbknKFGjnC2FQ0hJMzBFREdFMDMxMwBFZGdl
|
|
Locale: it_IT-ubuntu-22.04
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/FXEaAAAAADI7tKWNn8HTo+qT+EMRd8nQ0hJMzBFREdFMDMxMwBFZGdl
|
|
Locale: it_IT-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Locale: it_IT-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Minimum Versions-ubuntu-22.04
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>0SFzEaAAAAAAiN8tvhrReRLSF62fLSSCXQ0hJMzBFREdFMDQxMABFZGdl
|
|
Minimum Versions-ubuntu-22.04
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>0xFXEaAAAAAAbB0BVGSNCTrXIZwmp6RK9Q0hJMzBFREdFMDQxMABFZGdl
|
|
Minimum Versions-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Minimum Versions-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.12-ubuntu-22.04
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>0TFzEaAAAAABQdKAv+twfQqCEBsfVKTZ0QkwyQUEyMDMwMTA3MDI5AEVkZ2U=
|
|
Copy-on-Write 3.12-ubuntu-22.04
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>05FXEaAAAAAAyKEjOn+F8SoEDB8pO0xbpQkwyQUEyMDMwMTA3MDI5AEVkZ2U=
|
|
Copy-on-Write 3.12-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.12-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.10-ubuntu-22.04
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>0WFzEaAAAAABCUS7ncwBRRr1L3JUXvaDYQlkzRURHRTA0MTgARWRnZQ==
|
|
Copy-on-Write 3.10-ubuntu-22.04
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>071XEaAAAAABaZ3S8DdK0T4fNLwMmzqQ6QlkzRURHRTA0MTgARWRnZQ==
|
|
Copy-on-Write 3.10-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.10-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.9-ubuntu-22.04
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>0W1zEaAAAAACoCXrxTgMAQ5K0SYal6jhjQkwyQUEyMDMwMTA5MDQ5AEVkZ2U=
|
|
Copy-on-Write 3.9-ubuntu-22.04
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>0wlXEaAAAAAB5brMEpERIQbcxoFeBnszdQkwyQUEyMDMwMTA5MDQ5AEVkZ2U=
|
|
Copy-on-Write 3.9-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.9-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
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>0i1zEaAAAAADJtyR1Ci66TrbCut5YDMgnQkwyQUEyMDMwMTA5MDMxAEVkZ2U=
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
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>001XEaAAAAACsn4uO6X3oSJjomblUrIoeQkwyQUEyMDMwMTA4MDUxAEVkZ2U=
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
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>0j1zEaAAAAAAQ5toVklMPRrTf3vHB6nBVRE0yRURHRTA5MTEARWRnZQ==
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 2
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
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>09FXEaAAAAACSrwyHVfEqSaYhNl3HuQL1RE0yRURHRTA5MTEARWRnZQ==
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
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>0mlzEaAAAAACepS6nERztQYLSrlasn6urQkwyQUEyMDMwMTA4MDA5AEVkZ2U=
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
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>0AFbEaAAAAADtiNWQ0+UEQIETHXDXbmEfQkwyQUEyMDMwMTA4MDA5AEVkZ2U=
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
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>09l3EaAAAAADCr1pxW7ExR4Y75/MrDA+pQ0hJMzBFREdFMDIwNgBFZGdl
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
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+lXEaAAAAACuKRqVRgXIQo+Cge+MGuVuQ0hJMzBFREdFMDIwNgBFZGdl
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
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>0K17EaAAAAABX6T4ub2wwQLj0bN4VLp2jU04xRURHRTE5MDcARWRnZQ==
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 2
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
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>02lXEaAAAAABnoAwt4ksDR5GftGPbGODBU04xRURHRTE5MDcARWRnZQ==
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
Failed to restore: Cache service responded with 400
|
|
Future infer strings-ubuntu-22.04
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>0RV7EaAAAAAD1bSxanqsxR7Ldtx3K7sBrUEhYMzFFREdFMDIxMwBFZGdl
|
|
Future infer strings-ubuntu-22.04
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>07FXEaAAAAABi5R2/Sx9DRIBkeFOdDUwxUEhYMzFFREdFMDIxMwBFZGdl
|
|
Future infer strings-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Future infer strings-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
macos-14 actions-312.yaml
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>0hl7EaAAAAAAZr1SQPwI8QagmpTZw4xtDQlkzRURHRTAyMTMARWRnZQ==
|
|
macos-14 actions-312.yaml
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>091XEaAAAAABnuNov0f1FSKsTR6MwMEl+UEFPRURHRTA2MTYARWRnZQ==
|
|
macos-14 actions-312.yaml
Failed to restore: Cache service responded with 400
|
|
macos-14 actions-312.yaml
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
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>0m17EaAAAAACbu/Uh5/nKRZMhamElyBzUU04xRURHRTE4MTgARWRnZQ==
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 2
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
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>06FXEaAAAAAA4IW0BxvmFTroz1pi5ZQPMU04xRURHRTE4MTgARWRnZQ==
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Failed to restore: Cache service responded with 400
|
|
windows-latest actions-39.yaml
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>0L1/EaAAAAAB2ncGvq4vESJviHC0lkH1zQkwyQUEyMDMwMTA3MDM5AEVkZ2U=
|
|
windows-latest actions-39.yaml
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>0H1bEaAAAAACgQ6EAv5HOS5eF8IFRHdWvQkwyQUEyMDMwMTA3MDM5AEVkZ2U=
|
|
windows-latest actions-39.yaml
Failed to restore: Cache service responded with 400
|
|
windows-latest actions-39.yaml
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
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>0OF/EaAAAAADUdqTyHupjQLc80tJZt8lkQkwyQUEyMDMwMTA1MDM5AEVkZ2U=
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 2
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
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>04lXEaAAAAACQcOWNo92iQI6OCVCtuAhHQkwyQUEyMDMwMTA1MDM5AEVkZ2U=
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Failed to restore: Cache service responded with 400
|
|
macos-14 actions-310.yaml
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>03V/EaAAAAAAoTvK0lrUuRIEGeeGvWzIHQkwyQUEyMDMwMTA1MDM5AEVkZ2U=
|
|
macos-14 actions-310.yaml
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>09lXEaAAAAABbn4b7v4RcSZ9pkPq8JXEHQkwyQUEyMDMwMTA5MDM3AEVkZ2U=
|
|
macos-14 actions-310.yaml
Failed to restore: Cache service responded with 400
|
|
macos-14 actions-310.yaml
Failed to restore: Cache service responded with 400
|
|
windows-latest actions-310.yaml
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>0GWDEaAAAAACrFN+btah5Q6CWgZGixkIbRE0yRURHRTA3MTMARWRnZQ==
|
|
windows-latest actions-310.yaml
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>0XlbEaAAAAACJkhVx01a4Tr2ar6sWE3CfRE0yRURHRTA3MTMARWRnZQ==
|
|
windows-latest actions-310.yaml
Failed to restore: Cache service responded with 400
|
|
windows-latest actions-310.yaml
Failed to restore: Cache service responded with 400
|
|
windows-latest actions-312.yaml
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>0G2DEaAAAAACi7yPzsp1tQbch5/rWVYiyQ0hJMzBFREdFMDEwNwBFZGdl
|
|
windows-latest actions-312.yaml
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>0oFbEaAAAAACf+VKDP8IKRqZ7xgaVaP4RQ0hJMzBFREdFMDExOQBFZGdl
|
|
windows-latest actions-312.yaml
Failed to restore: Cache service responded with 400
|
|
windows-latest actions-312.yaml
Failed to restore: Cache service responded with 400
|
|
macos-13 actions-39.yaml
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>0Y2DEaAAAAAAkDyrOoMXeRa8qozjCOLX4QlkzRURHRTA1MTkARWRnZQ==
|
|
macos-13 actions-39.yaml
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>0J1bEaAAAAADglDcvnxJwQYsTY1eFWEEHUEFPRURHRTA1MTYARWRnZQ==
|
|
macos-13 actions-39.yaml
Failed to restore: Cache service responded with 400
|
|
macos-13 actions-39.yaml
Failed to restore: Cache service responded with 400
|
|
windows-latest actions-311.yaml
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>0eWDEaAAAAACq30ucO1NuSKkqZGfbXVWBUEFPRURHRTA2MTcARWRnZQ==
|
|
windows-latest actions-311.yaml
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>0ZlbEaAAAAABjcCZPkMtXQIG3Xbx7a5s/UEFPRURHRTA2MTcARWRnZQ==
|
|
windows-latest actions-311.yaml
Failed to restore: Cache service responded with 400
|
|
windows-latest actions-311.yaml
Failed to restore: Cache service responded with 400
|
|
macos-14 actions-311.yaml
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>0zmDEaAAAAADO39lG5FvAQYTxZAJAsb8PQkwyQUEyMDMwMTA5MDI1AEVkZ2U=
|
|
macos-14 actions-311.yaml
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>0JFbEaAAAAABKuZa2PF5/S6FKiFZgZuo6QkwyQUEyMDMwMTA3MDMzAEVkZ2U=
|
|
macos-14 actions-311.yaml
Failed to restore: Cache service responded with 400
|
|
macos-14 actions-311.yaml
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
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>0D2HEaAAAAABvnOH642rcTZZ6tt8UUzXnQkwyQUEyMDMwMTA2MDA3AEVkZ2U=
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
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>0wFXEaAAAAAAzbWMn1d2pRLuKBXDEl0cIQkwyQUEyMDMwMTA2MDA3AEVkZ2U=
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
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>0LWHEaAAAAACALsVLZq3WRbLXWeZWUEp8UEFPRURHRTA1MjIARWRnZQ==
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
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>07VXEaAAAAAAzM2VRdsl+TobaWoi9olK0UEFPRURHRTA1MjIARWRnZQ==
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
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>0lWHEaAAAAABXbPtFs5IfTYUN+F9hopRbUEhYMzFFREdFMDUxNABFZGdl
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
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/FXEaAAAAADB9nlfdqnHRZwzKGSO1rlQUEhYMzFFREdFMDUxNABFZGdl
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
macos-14 actions-39.yaml
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>0G2LEaAAAAABaxXpKRzXXSJC6cNWfIs1gU04xRURHRTE2MTQARWRnZQ==
|
|
macos-14 actions-39.yaml
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>0FFbEaAAAAABt+EdDMPrCRKhw9T8ShB9nU04xRURHRTE1MDkARWRnZQ==
|
|
macos-14 actions-39.yaml
Failed to restore: Cache service responded with 400
|
|
macos-14 actions-39.yaml
Failed to restore: Cache service responded with 400
|
|
macos-13 actions-312.yaml
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>0rWLEaAAAAAA2qd4UeS+RRZgBOfqwj7bzUEFPRURHRTA1MTAARWRnZQ==
|
|
macos-13 actions-312.yaml
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>0PlbEaAAAAACNa0vRY/2wRJp76rdK62XsQlkzRURHRTA1MTQARWRnZQ==
|
|
macos-13 actions-312.yaml
Failed to restore: Cache service responded with 400
|
|
macos-13 actions-312.yaml
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
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>0PGXEaAAAAAAyrGMl4ypNR6QHQ0gMWUQDQ0hJMzBFREdFMDMwOQBFZGdl
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
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>0J1bEaAAAAAAknmBo4ZuvS5owFXwMi8GKQ0hJMzBFREdFMDMwOQBFZGdl
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Failed to restore: Cache service responded with 400
|
|
macos-13 actions-311.yaml
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>0kmbEaAAAAACz5pVv+zj6QaHinMfO4x/vQlkzRURHRTAzMTkARWRnZQ==
|
|
macos-13 actions-311.yaml
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>0zlbEaAAAAACncqkTKMMJQLaBrq+LYrJ6UEFPRURHRTA1MjEARWRnZQ==
|
|
macos-13 actions-311.yaml
Failed to restore: Cache service responded with 400
|
|
macos-13 actions-311.yaml
Failed to restore: Cache service responded with 400
|
|
macos-13 actions-310.yaml
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+GfEaAAAAAB/hL5Ve0XMQJGVV5WpfDqYQkwyQUEyMDMwMTA1MDA3AEVkZ2U=
|
|
macos-13 actions-310.yaml
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>0lFbEaAAAAAAXEDFnKctvSKl9/shvmHFJQkwyQUEyMDMwMTA2MDA1AEVkZ2U=
|
|
macos-13 actions-310.yaml
Failed to restore: Cache service responded with 400
|
|
macos-13 actions-310.yaml
Failed to restore: Cache service responded with 400
|
|
python-dev (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
|
|
windows-latest actions-39.yaml
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
|
|
windows-latest actions-310.yaml
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
|
|
windows-latest actions-312.yaml
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
|
|
windows-latest actions-311.yaml
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
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Test results
|
1.46 MB |
sha256:bb8881aa6d422eda29041ab937b0a838eae7514eab420816872f61eafc302aa2
|
|