[backport 2.3.x] BUG(string dtype): groupby/resampler.min/max returns float on all NA strings (#60985) #23819
jorisvandenbosscheunit-tests.yml
on: pull_request
Linux-32-bit
20m 30s
Linux-Musl
21m 33s
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Annotations
71 errors and 117 warnings
|
python-dev (macOS-14)
Process completed with exit code 1.
|
|
Linux-32-bit
Process completed with exit code 1.
|
|
Linux-Musl
Process completed with exit code 1.
|
|
Numpy Dev-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Numpy Dev-ubuntu-22.04
Process completed with exit code 1.
|
|
python-dev (ubuntu-22.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-22.04)
Process completed with exit code 1.
|
|
Pyarrow Nightly-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Pyarrow Nightly-ubuntu-22.04
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.
|
|
Minimum Versions-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Minimum Versions-ubuntu-22.04
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.
|
|
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.
|
|
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-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.
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Process completed with exit code 1.
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Process completed with exit code 1.
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
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.
|
|
Copy-on-Write 3.11-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.11-ubuntu-22.04
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.
|
|
Copy-on-Write 3.12-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.12-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Process completed with exit code 1.
|
|
Locale: it_IT-ubuntu-22.04
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-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Process completed with exit code 1.
|
|
Locale: zh_CN-ubuntu-22.04
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-ubuntu-22.04
Process completed with exit code 1.
|
|
Copy-on-Write 3.10-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Copy-on-Write 3.10-ubuntu-22.04
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-latest actions-312.yaml-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Process completed with exit code 1.
|
|
Future infer strings-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Future infer strings-ubuntu-22.04
Process completed with exit code 1.
|
|
windows-latest actions-311.yaml
EPERM: operation not permitted, unlink 'C:\Users\runneradmin\micromamba\pkgs\libzlib-1.3.1-h2466b09_2\zlib.dll'
|
|
windows-latest actions-311.yaml
The operation was canceled.
|
|
windows-latest actions-311.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
windows-latest actions-310.yaml
EPERM: operation not permitted, unlink 'C:\Users\runneradmin\micromamba\pkgs\libzlib-1.3.1-h2466b09_2\zlib.dll'
|
|
windows-latest actions-310.yaml
The operation was canceled.
|
|
windows-latest actions-310.yaml
The job has exceeded the maximum execution time of 1h30m0s
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
The operation was canceled.
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Process completed with exit code 1.
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
The job has exceeded the maximum execution time of 1h30m0s
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
The operation was canceled.
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Process completed with exit code 1.
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
The job has exceeded the maximum execution time of 1h30m0s
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
The operation was canceled.
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Process completed with exit code 1.
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
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
|
|
Downstream Compat-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Downstream Compat-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Downstream Compat-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Downstream Compat-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Pypy-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Pypy-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Pypy-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Pypy-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Numpy Dev-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Numpy Dev-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Numpy Dev-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Numpy Dev-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Pyarrow Nightly-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Pyarrow Nightly-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Pyarrow Nightly-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Pyarrow Nightly-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Minimum Versions-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Minimum Versions-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Minimum Versions-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Minimum Versions-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-14 actions-311.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-14 actions-311.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-14 actions-311.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-14 actions-311.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-14 actions-310.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-14 actions-310.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-14 actions-310.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-14 actions-310.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-14 actions-312.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-14 actions-312.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-14 actions-312.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-14 actions-312.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 2
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-312.yaml-ubuntu-24.04-arm
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 2
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-311.yaml-ubuntu-24.04-arm
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 2
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-310.yaml-ubuntu-24.04-arm
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-13 actions-311.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-13 actions-311.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-13 actions-311.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-13 actions-311.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.11-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.11-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.11-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.11-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-13 actions-312.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-13 actions-312.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-13 actions-312.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-13 actions-312.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.12-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.12-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.12-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.12-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.11 (warnings)-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Locale: it_IT-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Locale: it_IT-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Locale: it_IT-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Locale: it_IT-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.10 (warnings)-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Locale: zh_CN-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Locale: zh_CN-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Locale: zh_CN-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Locale: zh_CN-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.10-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.10-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Copy-on-Write 3.10-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Copy-on-Write 3.10-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-13 actions-310.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-13 actions-310.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
macos-13 actions-310.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
macos-13 actions-310.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-312.yaml-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Future infer strings-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Future infer strings-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Future infer strings-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Future infer strings-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
windows-latest actions-311.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
windows-latest actions-311.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
windows-latest actions-311.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
windows-latest actions-310.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
windows-latest actions-310.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
windows-latest actions-310.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
Future infer strings (without pyarrow)-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-311.yaml-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Failed to save: reserveCache failed: Cache service responded with 503
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
ubuntu-latest actions-310.yaml-ubuntu-22.04
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
windows-latest actions-312.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
windows-latest actions-312.yaml
Failed to save: reserveCache failed: Cache service responded with 503
|
|
windows-latest actions-312.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
|
windows-latest actions-312.yaml
Failed to restore: getCacheEntry failed: Cache service responded with 503
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Test results
|
1.29 MB |
sha256:0cb3d0b6861b81fc6debcc4f251d61fe602d8e7ecf09e75a321686686a5115f1
|
|