Skip to content

PARTIAL FIX: Improve leading zeros preservation with dtype=str for dict-based dtypes #25441

PARTIAL FIX: Improve leading zeros preservation with dtype=str for dict-based dtypes

PARTIAL FIX: Improve leading zeros preservation with dtype=str for dict-based dtypes #25441

Triggered via pull request September 2, 2025 21:03
@dxdcdxdc
synchronize #62242
dxdc:patch-2
Status Failure
Total duration 32m 11s
Artifacts 1

unit-tests.yml

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

Annotations

62 errors, 3 warnings, and 3 notices
Pyodide build
Process completed with exit code 2.
Linux-Musl
Process completed with exit code 2.
Linux-32-bit
Process completed with exit code 2.
Numpy Dev
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.
Pyarrow Nightly
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Pyarrow Nightly
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.
Freethreading
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Freethreading
Process completed with exit code 1.
Without PyArrow
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Without PyArrow
Process completed with exit code 1.
ubuntu-24.04-arm 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-24.04-arm actions-311.yaml
Process completed with exit code 2.
ubuntu-24.04-arm 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-24.04-arm actions-311.yaml
Process completed with exit code 1.
ubuntu-24.04-arm 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-24.04-arm actions-312.yaml
Process completed with exit code 2.
ubuntu-24.04-arm 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-24.04-arm actions-312.yaml
Process completed with exit code 1.
ubuntu-24.04-arm actions-313.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-24.04-arm actions-313.yaml
Process completed with exit code 2.
ubuntu-24.04-arm actions-313.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-24.04-arm actions-313.yaml
Process completed with exit code 1.
Minimum Versions
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Minimum Versions
Process completed with exit code 1.
ubuntu-24.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-24.04 actions-311.yaml
Process completed with exit code 2.
ubuntu-24.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-24.04 actions-311.yaml
Process completed with exit code 1.
Locale: it_IT
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
Process completed with exit code 1.
Locale: zh_CN
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
Process completed with exit code 1.
ubuntu-24.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-24.04 actions-312.yaml
Process completed with exit code 2.
ubuntu-24.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-24.04 actions-312.yaml
Process completed with exit code 1.
ubuntu-24.04 actions-313.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-24.04 actions-313.yaml
Process completed with exit code 2.
ubuntu-24.04 actions-313.yaml
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
ubuntu-24.04 actions-313.yaml
Process completed with exit code 1.
PANDAS_FUTURE_INFER_STRING=0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
PANDAS_FUTURE_INFER_STRING=0
Process completed with exit code 2.
PANDAS_FUTURE_INFER_STRING=0
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
PANDAS_FUTURE_INFER_STRING=0
Process completed with exit code 1.
macos-14 actions-313.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-313.yaml
Process completed with exit code 1.
windows-latest actions-311.yaml
The operation was canceled.
windows-latest actions-311.yaml
Canceling since a higher priority waiting request for refs/pull/62242/merge-actions-311.yaml-windows-latest exists
windows-latest actions-312.yaml
The operation was canceled.
windows-latest actions-312.yaml
Canceling since a higher priority waiting request for refs/pull/62242/merge-actions-312.yaml-windows-latest exists
windows-latest actions-313.yaml
The operation was canceled.
windows-latest actions-313.yaml
Canceling since a higher priority waiting request for refs/pull/62242/merge-actions-313.yaml-windows-latest exists
macos-13 actions-313.yaml
The operation was canceled.
macos-13 actions-313.yaml
Canceling since a higher priority waiting request for refs/pull/62242/merge-actions-313.yaml-macos-13 exists
macos-13 actions-312.yaml
The operation was canceled.
macos-13 actions-312.yaml
Canceling since a higher priority waiting request for refs/pull/62242/merge-actions-312.yaml-macos-13 exists
macos-13 actions-311.yaml
The operation was canceled.
macos-13 actions-311.yaml
Canceling since a higher priority waiting request for refs/pull/62242/merge-actions-311.yaml-macos-13 exists
Pyodide build
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>061u3aAAAAAB4bM2tk32JRIthoZQmkciMUEFPRURHRTA2MDgARWRnZQ==
Pyodide build
No cached files found at path "/home/runner/work/pandas/pandas/emsdk-cache" - downloading and caching emsdk.
Pyodide build
Failed to restore: Cache service responded with 400
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
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-313.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 Expired
1.31 MB
sha256:6e0ccc22f6e8a24afbe291124d6689f1ebb2b43a024465252f80b4ba766b1c4e