Skip to content

API: mode.nan_is_na to consistently distinguish NaN-vs-NA #25622

API: mode.nan_is_na to consistently distinguish NaN-vs-NA

API: mode.nan_is_na to consistently distinguish NaN-vs-NA #25622

Triggered via pull request September 8, 2025 17:04
Status Failure
Total duration 1h 2m 17s
Artifacts 1

unit-tests.yml

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

Annotations

53 errors, 3 warnings, and 3 notices
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.
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.
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.
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.
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.
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.
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.
ubuntu-24.04-arm actions-313.yaml
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 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 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 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 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.
windows-latest 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
windows-latest actions-313.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.
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.
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.
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.
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.
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-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 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 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.
macos-13 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-13 actions-313.yaml
Process completed with exit code 1.
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>00wy/aAAAAACsFYBjV6EvSp387khludlaQlkzRURHRTA0MTQARWRnZQ==
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-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
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
1.52 MB
sha256:935177bc5a442fcb9fb6d4c76273d0d11d641bd7ccc81c60866cafef6773e537