Data frame snapshots #27332
AkiTheMemeGodunit-tests.yml
on: pull_request
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Annotations
56 errors and 27 warnings
|
Freethreading
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.
|
|
python-dev (macOS-14)
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-14)
Process completed with exit code 1.
|
|
Linux-Musl
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.
|
|
python-dev (windows-2025)
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-2025)
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.
|
|
Linux-32-bit
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.
|
|
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.
|
|
macos-15 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-15 actions-313.yaml
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-15 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-15 actions-311.yaml
Process completed with exit code 1.
|
|
macos-15 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-15 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 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 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.
|
|
windows-2025 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-2025 actions-311.yaml
Process completed with exit code 1.
|
|
windows-2025 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-2025 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.
|
|
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-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-15-intel 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-15-intel actions-313.yaml
Process completed with exit code 1.
|
|
windows-2025 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-2025 actions-313.yaml
Process completed with exit code 1.
|
|
macos-15-intel 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-15-intel actions-311.yaml
Process completed with exit code 1.
|
|
macos-15-intel 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-15-intel actions-312.yaml
Process completed with exit code 1.
|
|
Downstream Compat
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.
|
|
Numpy Dev
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, 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.
|
|
Without PyArrow
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-64, 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>0Tpb8aAAAAADliz4o6tgRSq3iF8q2lRGDUEhMMzBFREdFMDExNABFZGdl
|
|
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: 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-7f980036a54bf9b731e96423dab2167633dab2652673dc4fef598b730ac364cb-file-51e02878e993e3dd6975f339272bcdb9fe8c1f2ffa4baf8dd6936408bbe25d4d, 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.
|
|
macos-15 actions-311.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-arm64, another job may be creating this cache.
|
|
macos-15 actions-312.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-arm64, 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.
|
|
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.
|
|
windows-2025 actions-312.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-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-7f980036a54bf9b731e96423dab2167633dab2652673dc4fef598b730ac364cb-file-2ea4b81a7e08391d0a2ed43da8b6b8c3b4f57de6eb248bb889a4bff2c17c4048, 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.
|
|
PANDAS_FUTURE_INFER_STRING=0
Failed to save: Unable to reserve cache with key micromamba-environment--linux-64-test-args-4f53cda-root-dcc80ee-bin-7f980036a54bf9b731e96423dab2167633dab2652673dc4fef598b730ac364cb-file-51e02878e993e3dd6975f339272bcdb9fe8c1f2ffa4baf8dd6936408bbe25d4d, 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-313.yaml
Failed to save: Unable to reserve cache with key micromamba-environment--linux-64-test-args-4f53cda-root-dcc80ee-bin-7f980036a54bf9b731e96423dab2167633dab2652673dc4fef598b730ac364cb-file-51e02878e993e3dd6975f339272bcdb9fe8c1f2ffa4baf8dd6936408bbe25d4d, another job may be creating this cache.
|
|
windows-2025 actions-313.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--win-64, another job may be creating this cache.
|
|
macos-15-intel actions-311.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-64, another job may be creating this cache.
|
|
macos-15-intel actions-312.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-64, another job may be creating this cache.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Test results
|
1.3 MB |
sha256:2bc73cca576f99fd2f7361453b5d546673a96f627b8f5fb78a764bef2d799e86
|
|