Skip to content

Flattened footer #24865

Flattened footer

Flattened footer #24865

Triggered via pull request August 2, 2025 03:02
Status Failure
Total duration 48m 28s
Artifacts 1

unit-tests.yml

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

Annotations

76 errors, 3 warnings, and 4 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-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.
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.
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.
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.
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.
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.
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-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.
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.
ubuntu-24.04-arm 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
ubuntu-24.04-arm actions-310.yaml
Process completed with exit code 2.
ubuntu-24.04-arm 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
ubuntu-24.04-arm actions-310.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.
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-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-14 actions-310.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.
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.
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.
ubuntu-24.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
ubuntu-24.04 actions-310.yaml
Process completed with exit code 2.
ubuntu-24.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
ubuntu-24.04 actions-310.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 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.
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.
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.
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-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-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.
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.
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.
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>0GoCNaAAAAAAnE1WhogFIT5wgs22oRw/ZRE0yRURHRTA0MTEARWRnZQ==
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-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-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.29 MB
sha256:049c29af7abf9e3b05fa2ad0848179b8326c81d0b47a60bd1c01b396136d5e86