BUG: Fix pd.read_csv
doesn't skip bad line if it is the 1st line of the chunk
#25923
unit-tests.yml
on: pull_request
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Annotations
56 errors, 26 warnings, and 4 notices
python-dev (macOS-13)
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 (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.
|
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.
|
Linux-32-bit
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.
|
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.
|
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.
|
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.
|
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.
|
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.
|
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-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-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.
|
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-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.
|
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.
|
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.
|
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.
|
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.
|
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.
|
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.
|
Freethreading
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>0m8LOaAAAAAA7Ajul8LiORaCQOKpm+IIyUEFPRURHRTA1MjAARWRnZQ==
|
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
|
macos-14 actions-313.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--osx-arm64, 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.
|
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: zh_CN
Failed to save: Unable to reserve cache with key micromamba-environment--linux-64-test-args-4f53cda-root-dcc80ee-bin-d2edc1ba4d7ee2a8dabe8913906c08a42cf169bb65e50fc0d53a37b44e2bdd1e-file-dcb18d4e381a0a935d1e37d4e449872f3e448eead330bbb0770b27e4a274c30e, 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-d2edc1ba4d7ee2a8dabe8913906c08a42cf169bb65e50fc0d53a37b44e2bdd1e-file-dcb18d4e381a0a935d1e37d4e449872f3e448eead330bbb0770b27e4a274c30e, 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-arm actions-313.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--linux-aarch64, another job may be creating this cache.
|
windows-latest actions-311.yaml
Failed to save: Unable to reserve cache with key micromamba-downloads--win-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.
|
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.
|
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.
|
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-d2edc1ba4d7ee2a8dabe8913906c08a42cf169bb65e50fc0d53a37b44e2bdd1e-file-2c0cfead90ca67bf70a0971a6eec4396d8b654a77c399c4dfdb00859159ee268, 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.
|
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-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-d2edc1ba4d7ee2a8dabe8913906c08a42cf169bb65e50fc0d53a37b44e2bdd1e-file-dcb18d4e381a0a935d1e37d4e449872f3e448eead330bbb0770b27e4a274c30e, another job may be creating this cache.
|
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-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
|
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.29 MB |
sha256:dbef79da1df2071e1651183186f763bd588dac2570956bbefc55300c5f8a4e2d
|
|