Skip to content

BUG: Take method of NumpyExtensionArray now returns another extension array with the correct dtype. #26228

BUG: Take method of NumpyExtensionArray now returns another extension array with the correct dtype.

BUG: Take method of NumpyExtensionArray now returns another extension array with the correct dtype. #26228

Triggered via pull request September 29, 2025 17:52
Status Failure
Total duration 1h 34m 57s
Artifacts 1

unit-tests.yml

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

Annotations

70 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.
python-dev (macOS-14)
Process completed with exit code 1.
python-dev (ubuntu-24.04)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
python-dev (ubuntu-24.04)
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.
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.
python-dev (windows-latest)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
python-dev (windows-latest)
Process completed with exit code 1.
Numpy Dev
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Numpy Dev
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-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.
python-dev (macOS-13)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
python-dev (macOS-13)
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.
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-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.
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-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-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-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.
Without PyArrow
The operation was canceled.
Without PyArrow
The job has exceeded the maximum execution time of 1h30m0s
windows-latest actions-313.yaml
The operation was canceled.
windows-latest actions-313.yaml
The job has exceeded the maximum execution time of 1h30m0s
windows-latest actions-311.yaml
The operation was canceled.
windows-latest actions-311.yaml
The job has exceeded the maximum execution time of 1h30m0s
macos-13 actions-311.yaml
The operation was canceled.
macos-13 actions-311.yaml
The job has exceeded the maximum execution time of 1h30m0s
windows-latest actions-312.yaml
The operation was canceled.
windows-latest actions-312.yaml
The job has exceeded the maximum execution time of 1h30m0s
macos-14 actions-311.yaml
The operation was canceled.
macos-14 actions-311.yaml
The job has exceeded the maximum execution time of 1h30m0s
macos-13 actions-313.yaml
The operation was canceled.
macos-13 actions-313.yaml
The job has exceeded the maximum execution time of 1h30m0s
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
The operation was canceled.
ubuntu-24.04 actions-311.yaml
The job has exceeded the maximum execution time of 1h30m0s
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
The operation was canceled.
ubuntu-24.04 actions-312.yaml
The job has exceeded the maximum execution time of 1h30m0s
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>0kMfaaAAAAABEB3J5VSefTbGB8FLaCZSvUEhMMzBFREdFMDIxMwBFZGdl
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
python-dev (windows-latest)
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
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

Artifacts

Produced during runtime
Name Size Digest
Test results
3.53 MB
sha256:65094a4d18ebef4973df58469f649f581fbb94c8cd7e6e841e7c7937728bac83