Skip to content

[WIP] df.apply: add support for engine='bodo' #21146

[WIP] df.apply: add support for engine='bodo'

[WIP] df.apply: add support for engine='bodo' #21146

Triggered via pull request December 30, 2024 20:29
Status Failure
Total duration 47m 12s
Artifacts 1

unit-tests.yml

on: pull_request
Matrix: macos-windows
Matrix: python-dev
Matrix: ubuntu
Fit to window
Zoom out
Zoom in

Annotations

27 errors
macos-14 actions-312.yaml
The process '/Users/runner/micromamba-bin/micromamba' failed with exit code 1
macos-14 actions-312.yaml
ENOENT: no such file or directory, lstat '/Users/runner/work/_temp/setup-micromamba/micromamba-shell'
macos-14 actions-310.yaml
The process '/Users/runner/micromamba-bin/micromamba' failed with exit code 1
macos-14 actions-310.yaml
ENOENT: no such file or directory, lstat '/Users/runner/work/_temp/setup-micromamba/micromamba-shell'
macos-14 actions-311.yaml
The process '/Users/runner/micromamba-bin/micromamba' failed with exit code 1
macos-14 actions-311.yaml
ENOENT: no such file or directory, lstat '/Users/runner/work/_temp/setup-micromamba/micromamba-shell'
macos-13 actions-311.yaml
The process '/Users/runner/micromamba-bin/micromamba' failed with exit code 1
macos-13 actions-311.yaml
ENOENT: no such file or directory, lstat '/Users/runner/work/_temp/setup-micromamba/micromamba-shell'
Minimum Versions
The process '/home/runner/micromamba-bin/micromamba' failed with exit code 1
Minimum Versions
ENOENT: no such file or directory, lstat '/home/runner/work/_temp/setup-micromamba/micromamba-shell'
macos-13 actions-310.yaml
The process '/Users/runner/micromamba-bin/micromamba' failed with exit code 1
macos-13 actions-310.yaml
ENOENT: no such file or directory, lstat '/Users/runner/work/_temp/setup-micromamba/micromamba-shell'
macos-13 actions-312.yaml
The process '/Users/runner/micromamba-bin/micromamba' failed with exit code 1
macos-13 actions-312.yaml
ENOENT: no such file or directory, lstat '/Users/runner/work/_temp/setup-micromamba/micromamba-shell'
windows-latest actions-311.yaml
The process 'C:\Users\runneradmin\micromamba-bin\micromamba.exe' failed with exit code 1
windows-latest actions-311.yaml
Could not find micromamba activate test in C:\Users\runneradmin\.bash_profile
windows-latest actions-310.yaml
The process 'C:\Users\runneradmin\micromamba-bin\micromamba.exe' failed with exit code 1
windows-latest actions-310.yaml
Could not find micromamba activate test in C:\Users\runneradmin\.bash_profile
windows-latest actions-312.yaml
The process 'C:\Users\runneradmin\micromamba-bin\micromamba.exe' failed with exit code 1
windows-latest actions-312.yaml
Could not find micromamba activate test in C:\Users\runneradmin\.bash_profile
Future infer strings (without pyarrow)
Process completed with exit code 1.
Future infer strings
The hosted runner: GitHub Actions 118 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.
ubuntu-latest actions-310.yaml
The hosted runner: GitHub Actions 208 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.
ubuntu-latest actions-312.yaml
The hosted runner: GitHub Actions 155 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.
Locale: zh_CN
The hosted runner: GitHub Actions 396 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.
ubuntu-latest actions-311.yaml
The hosted runner: GitHub Actions 404 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.
Locale: it_IT
The hosted runner: GitHub Actions 349 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.

Artifacts

Produced during runtime
Name Size
Test results
1.36 MB