Modified merge method #25374
Triggered via pull request
August 29, 2025 01:04
abcds07
Status
Failure
Total duration
2h 13m 27s
Artifacts
1
unit-tests.yml
on: pull_request
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Annotations
52 errors, 3 warnings, and 3 notices
|
Linux-32-bit
Process completed with exit code 128.
|
|
Linux-Musl
Process completed with exit code 128.
|
|
Downstream Compat
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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-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
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-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.
|
|
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.
|
|
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.
|
|
windows-latest actions-312.yaml
The operation was canceled.
|
|
windows-latest actions-312.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
windows-latest actions-313.yaml
The operation was canceled.
|
|
Minimum Versions
The operation was canceled.
|
|
windows-latest actions-313.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
Minimum Versions
The job has exceeded the maximum execution time of 1h30m0s
|
|
ubuntu-24.04 actions-313.yaml
The operation was canceled.
|
|
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
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
|
|
macos-13 actions-313.yaml
The operation was canceled.
|
|
macos-13 actions-313.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
macos-13 actions-312.yaml
The operation was canceled.
|
|
macos-13 actions-312.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
Without PyArrow
The operation was canceled.
|
|
Without PyArrow
The job has exceeded the maximum execution time of 1h30m0s
|
|
ubuntu-24.04 actions-312.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
ubuntu-24.04-arm actions-312.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
ubuntu-24.04-arm actions-311.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
ubuntu-24.04 actions-311.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
Pyodide build
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>0zvywaAAAAABLW3kSRLi/QJ/ioBnMi13YQkwyQUEyMDMwMTA2MDM5AEVkZ2U=
|
|
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-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
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Test results
|
1.34 KB |
sha256:f3db3a80209ef2486d1d66ad1b13d02b02638467b244ab4493ae3dfae31482b9
|
|