Backport to 2.3.x: REGR: from_records not initializing subclasses pro… #26082
mroeschkeunit-tests.yml
on: push
Linux-32-bit
21m 2s
Linux-Musl
23m 52s
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Annotations
41 errors, 96 warnings, and 5 notices
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Copy-on-Write 3.10-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Minimum Versions-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Downstream Compat-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Pyarrow Nightly-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Pypy-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Copy-on-Write 3.11-ubuntu-22.04
Docker pull failed with exit code 1
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Numpy Dev-ubuntu-22.04
Docker pull failed with exit code 1
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1
|
|
Locale: zh_CN-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Copy-on-Write 3.12-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Locale: it_IT-ubuntu-22.04
Docker pull failed with exit code 1
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1
|
|
Future infer strings-ubuntu-22.04
Docker pull failed with exit code 1
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Docker pull failed with exit code 1
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1
|
|
Copy-on-Write 3.9-ubuntu-22.04
Docker pull failed with exit code 1
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Docker pull failed with exit code 1
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1
|
|
macos-14 actions-310.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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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-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
Docker pull failed with exit code 1, back off 2.571 seconds before retry.
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Docker pull failed with exit code 1, back off 3.907 seconds before retry.
|
|
Copy-on-Write 3.10-ubuntu-22.04
Docker pull failed with exit code 1, back off 1.422 seconds before retry.
|
|
Copy-on-Write 3.10-ubuntu-22.04
Docker pull failed with exit code 1, back off 3.436 seconds before retry.
|
|
Minimum Versions-ubuntu-22.04
Docker pull failed with exit code 1, back off 2.73 seconds before retry.
|
|
Minimum Versions-ubuntu-22.04
Docker pull failed with exit code 1, back off 3.496 seconds before retry.
|
|
Downstream Compat-ubuntu-22.04
Docker pull failed with exit code 1, back off 2.965 seconds before retry.
|
|
Downstream Compat-ubuntu-22.04
Docker pull failed with exit code 1, back off 4.502 seconds before retry.
|
|
Pyarrow Nightly-ubuntu-22.04
Docker pull failed with exit code 1, back off 4.18 seconds before retry.
|
|
Pyarrow Nightly-ubuntu-22.04
Docker pull failed with exit code 1, back off 1.43 seconds before retry.
|
|
Pypy-ubuntu-22.04
Docker pull failed with exit code 1, back off 1.647 seconds before retry.
|
|
Pypy-ubuntu-22.04
Docker pull failed with exit code 1, back off 5.048 seconds before retry.
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1, back off 1.977 seconds before retry.
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1, back off 1.027 seconds before retry.
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
Docker pull failed with exit code 1, back off 8.856 seconds before retry.
|
|
ubuntu-latest actions-39.yaml-ubuntu-22.04
Docker pull failed with exit code 1, back off 1.257 seconds before retry.
|
|
Copy-on-Write 3.11-ubuntu-22.04
Docker pull failed with exit code 1, back off 2.881 seconds before retry.
|
|
Copy-on-Write 3.11-ubuntu-22.04
Docker pull failed with exit code 1, back off 4.006 seconds before retry.
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Docker pull failed with exit code 1, back off 4.492 seconds before retry.
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Docker pull failed with exit code 1, back off 7.592 seconds before retry.
|
|
Numpy Dev-ubuntu-22.04
Docker pull failed with exit code 1, back off 7.385 seconds before retry.
|
|
Numpy Dev-ubuntu-22.04
Docker pull failed with exit code 1, back off 3.03 seconds before retry.
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1, back off 8.258 seconds before retry.
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1, back off 1.052 seconds before retry.
|
|
Locale: zh_CN-ubuntu-22.04
Docker pull failed with exit code 1, back off 8.764 seconds before retry.
|
|
Locale: zh_CN-ubuntu-22.04
Docker pull failed with exit code 1, back off 2.074 seconds before retry.
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1, back off 5.131 seconds before retry.
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1, back off 3.034 seconds before retry.
|
|
Copy-on-Write 3.12-ubuntu-22.04
Docker pull failed with exit code 1, back off 4.318 seconds before retry.
|
|
Copy-on-Write 3.12-ubuntu-22.04
Docker pull failed with exit code 1, back off 7.489 seconds before retry.
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1, back off 5.677 seconds before retry.
|
|
Copy-on-Write 3.9 (warnings)-ubuntu-22.04
Docker pull failed with exit code 1, back off 4.758 seconds before retry.
|
|
Locale: it_IT-ubuntu-22.04
Docker pull failed with exit code 1, back off 8.966 seconds before retry.
|
|
Locale: it_IT-ubuntu-22.04
Docker pull failed with exit code 1, back off 4.776 seconds before retry.
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1, back off 7.882 seconds before retry.
|
|
ubuntu-latest actions-39.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1, back off 1.555 seconds before retry.
|
|
Future infer strings-ubuntu-22.04
Docker pull failed with exit code 1, back off 5.049 seconds before retry.
|
|
Future infer strings-ubuntu-22.04
Docker pull failed with exit code 1, back off 8.805 seconds before retry.
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Docker pull failed with exit code 1, back off 6.647 seconds before retry.
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Docker pull failed with exit code 1, back off 8.683 seconds before retry.
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1, back off 3.259 seconds before retry.
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1, back off 6.435 seconds before retry.
|
|
Copy-on-Write 3.9-ubuntu-22.04
Docker pull failed with exit code 1, back off 9.477 seconds before retry.
|
|
Copy-on-Write 3.9-ubuntu-22.04
Docker pull failed with exit code 1, back off 7.585 seconds before retry.
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Docker pull failed with exit code 1, back off 5.634 seconds before retry.
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Docker pull failed with exit code 1, back off 8.593 seconds before retry.
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1, back off 9.789 seconds before retry.
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Docker pull failed with exit code 1, back off 4.94 seconds before retry.
|
|
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>0nYLUaAAAAADbMhEy9IAtS4mW+pSoqlUHU04xRURHRTE1MTEARWRnZQ==
|
|
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>053zUaAAAAADHZgBF3HTHRYa0c/NtJxK9U04xRURHRTI5MTkARWRnZQ==
|
|
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
|
|
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>0VoTUaAAAAABmB92cBltKQaR0EZS/cyApU04xRURHRTE4MTIARWRnZQ==
|
|
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>0KX3UaAAAAAAlbTIDw2aSRqV/M4NJNlKnU04xRURHRTMwMjAARWRnZQ==
|
|
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
|
|
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>0s4XUaAAAAAACruU0a6y9SZM/Fc62j5IOQkwyQUEyMDMwMTA4MDM1AEVkZ2U=
|
|
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>0OX3UaAAAAACViZfc6JFgQIgmiXge4d45QkwyQUEyMDMwMTA4MDM1AEVkZ2U=
|
|
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
|
|
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>0O4bUaAAAAAARwHZlxx8uToX61IaV7gr9U04xRURHRTIyMjEARWRnZQ==
|
|
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>0In3UaAAAAAD2PxD/MEC+RbOhvkGIzR78U04xRURHRTI5MDcARWRnZQ==
|
|
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
|
|
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>02obUaAAAAAAWWt3WI9SESI9rXKX6kDr2QkwyQUEyMDMwMTEwMDMxAEVkZ2U=
|
|
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>0cX3UaAAAAADinXjZHcrwQIGdezc5IlKgQkwyQUEyMDMwMTEwMDMxAEVkZ2U=
|
|
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
|
|
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>0M4fUaAAAAACYBu1e0Su2TYULzjYvGY3pQkwyQUEyMDMwMTA4MDM3AEVkZ2U=
|
|
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>0xH3UaAAAAABeGBP5Lt+aS5m6k5kR75P6QkwyQUEyMDMwMTA4MDM3AEVkZ2U=
|
|
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
|
|
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>0qIfUaAAAAAAN/4Iyx88CQai4tm3sklyEQkwyQUEyMDMwMTA4MDI1AEVkZ2U=
|
|
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>0On3UaAAAAAAUJT5+c4lWQoad96BQEeWeQkwyQUEyMDMwMTA4MDUzAEVkZ2U=
|
|
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
|
|
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>074jUaAAAAAA5Ql6dRmfGSraEuIr+9eaAUEFPRURHRTA2MDcARWRnZQ==
|
|
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>0QH3UaAAAAAA+5RdXHtFUR6gDoceg/XIaQlkzRURHRTA1MTAARWRnZQ==
|
|
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
|
|
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>0lonUaAAAAABV5X+zRelUTa+TsnsYRjr3Q0hJMzBFREdFMDEyMABFZGdl
|
|
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>08n/UaAAAAAC+FgT6h63GT78oH+T9C8q7Q0hJMzBFREdFMDEyMABFZGdl
|
|
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-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>0FYrUaAAAAAC7tN09ur0fS7nk5vMPiI5vU04xRURHRTE5MTAARWRnZQ==
|
|
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>0L33UaAAAAACsG/n6b39lRJqe3lqfPZ9CU04xRURHRTI5MjEARWRnZQ==
|
|
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>0HYrUaAAAAACEPbj3+BMTT5LbtKZ7K+sYU04xRURHRTE2MDYARWRnZQ==
|
|
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>0W33UaAAAAABLK/0F4C5JRr6qDMLlvmzMU04xRURHRTIyMDcARWRnZQ==
|
|
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
|
|
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>0QYrUaAAAAAAaOeR3ziIsSKK97RW7j7f8QkwyQUEyMDMwMTA5MDQ1AEVkZ2U=
|
|
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>0yn3UaAAAAACgbaR5Mmr4TK20tPcPWhYzQkwyQUEyMDMwMTA4MDMzAEVkZ2U=
|
|
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
|
|
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-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-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-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.42 MB |
sha256:781103716ba96d3a14ee13468e9d8b6d32735394cd0865c58cc365eebc4156a5
|
|