Skip to content

fix: address & / | operator errors for PySpark / chore: use F.lit in maybe_evaluate for pyspark, like we do for duckdb #6100

fix: address & / | operator errors for PySpark / chore: use F.lit in maybe_evaluate for pyspark, like we do for duckdb

fix: address & / | operator errors for PySpark / chore: use F.lit in maybe_evaluate for pyspark, like we do for duckdb #6100

Triggered via pull request January 27, 2025 08:15
Status Failure
Total duration 11m 30s
Artifacts

pytest.yml

on: pull_request
Matrix: pytest-38
Matrix: pytest-full-coverage
Matrix: pytest-windows
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
pytest-full-coverage (3.13, ubuntu-latest)
Process completed with exit code 1.
pytest-full-coverage (3.11, ubuntu-latest)
The job was canceled because "_3_13_ubuntu-latest" failed.
pytest-full-coverage (3.11, ubuntu-latest)
The operation was canceled.
pytest-windows (3.10, windows-latest)
Process completed with exit code 1.
pytest-38 (3.8, ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
pytest-full-coverage (3.13, ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636