Move chained assignment detection to cython for Python 3.14 compat #24986
jorisvandenbosscheunit-tests.yml
on: pull_request
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Annotations
75 errors, 30 warnings, and 4 notices
|
Downstream Compat
Process completed with exit code 1.
|
|
Linux-Musl
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.
|
|
Linux-32-bit
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.
|
|
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.
|
|
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.
|
|
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.
|
|
Pyodide build
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: 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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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-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.
|
|
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.
|
|
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-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.
|
|
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.
|
|
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.
|
|
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.
|
|
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-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-arm actions-310.yaml
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
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.
|
|
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.
|
|
Numpy Dev
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
macos-14 actions-311.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-arm64, another job may be creating this cache.
|
|
Pyarrow Nightly
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
Freethreading
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
macos-14 actions-312.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-arm64, another job may be creating this cache.
|
|
Without PyArrow
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
Without PyArrow
Failed to save: Unable to reserve cache with key micromamba-environment--linux-64-test-args-4f53cda-root-dcc80ee-bin-[object Promise]-file-8256072c79edda5978f2e2f28eb06ea542a8c1afa7e6402d2a25569154bce345, another job may be creating this cache.
|
|
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>0rLiVaAAAAABbsp8mC23SRrSrbVEj/MWjQkwyQUEyMDMwMTA2MDExAEVkZ2U=
|
|
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
|
|
Minimum Versions
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
Locale: zh_CN
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
Locale: it_IT
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
Locale: it_IT
Failed to save: Unable to reserve cache with key micromamba-environment--linux-64-test-args-4f53cda-root-dcc80ee-bin-[object Promise]-file-9221b3298b38c824989b4f82b54dd6ca7e26430cb2ee3a4ad9c6460f2573910d, another job may be creating this cache.
|
|
macos-14 actions-310.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-arm64, another job may be creating this cache.
|
|
macos-13 actions-310.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-64, another job may be creating this cache.
|
|
ubuntu-24.04-arm actions-313.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-aarch64, another job may be creating this cache.
|
|
ubuntu-24.04-arm actions-312.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-aarch64, another job may be creating this cache.
|
|
windows-latest actions-310.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--win-64, another job may be creating this cache.
|
|
windows-latest actions-312.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--win-64, another job may be creating this cache.
|
|
PANDAS_FUTURE_INFER_STRING=0
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
ubuntu-24.04 actions-311.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
ubuntu-24.04 actions-311.yaml
Failed to save: Unable to reserve cache with key micromamba-environment--linux-64-test-args-4f53cda-root-dcc80ee-bin-[object Promise]-file-9221b3298b38c824989b4f82b54dd6ca7e26430cb2ee3a4ad9c6460f2573910d, another job may be creating this cache.
|
|
ubuntu-24.04 actions-312.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
ubuntu-24.04 actions-312.yaml
Failed to save: Unable to reserve cache with key micromamba-environment--linux-64-test-args-4f53cda-root-dcc80ee-bin-[object Promise]-file-8256072c79edda5978f2e2f28eb06ea542a8c1afa7e6402d2a25569154bce345, another job may be creating this cache.
|
|
windows-latest actions-313.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--win-64, another job may be creating this cache.
|
|
ubuntu-24.04 actions-313.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
ubuntu-24.04 actions-310.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, another job may be creating this cache.
|
|
macos-13 actions-313.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-64, another job may be creating this cache.
|
|
macos-13 actions-311.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-64, another job may be creating this cache.
|
|
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-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
|
1.69 KB |
sha256:78684bade4cd22ad0163ff24dfd7a0ac14b044789f02946a68d6657af368abb9
|
|