BUG: fix read_json ignoring the dtype with the pyarrow engine #22131
unit-tests.yml
on: pull_request
Linux-32-bit
18m 6s
Linux-Musl
17m 31s
python-freethreading
23m 48s
Pyodide build
23m 15s
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
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
|
|