Skip to content

BUG: fix read_json ignoring the dtype with the pyarrow engine #22131

BUG: fix read_json ignoring the dtype with the pyarrow engine

BUG: fix read_json ignoring the dtype with the pyarrow engine #22131

Triggered via pull request February 24, 2025 14:59
Status Failure
Total duration 56m 27s
Artifacts 1

unit-tests.yml

on: pull_request
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Fit to window
Zoom out
Zoom in

Annotations

11 errors
Minimum Versions
Process completed with exit code 1.
Future infer strings (without pyarrow)
Process completed with exit code 1.
Future infer strings (without pyarrow)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-22.04 actions-311.yaml
Process completed with exit code 1.
ubuntu-22.04 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
ubuntu-22.04 actions-312.yaml
Process completed with exit code 1.
ubuntu-22.04 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
ubuntu-22.04 actions-310.yaml
Process completed with exit code 1.
ubuntu-22.04 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
Future infer strings
Process completed with exit code 1.
Future infer strings
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Artifacts

Produced during runtime
Name Size Digest
Test results Expired
1.5 MB
sha256:8c9b234d454a625ebf0495605de2c0af5955fa9e2e7642dbf0333ba5967f4336