Skip to content

ci

ci #17215

Triggered via schedule November 5, 2025 03:00
Status Failure
Total duration 24m 9s
Artifacts 1

ci.yml

on: schedule
python-filter
4s
python-filter
execution-filter
8s
execution-filter
lint (flake8)
21s
lint (flake8)
Test API, headers and no-engine mode
3m 44s
Test API, headers and no-engine mode
Matrix: test-all-unidist
Matrix: test-all
Matrix: test-sanity
Matrix: test-defaults
Matrix: test-native-dataframe-interoperability
Matrix: test-clean-install
Matrix: test-spreadsheet
test-asv-benchmarks
0s
test-asv-benchmarks
merge-coverage-artifacts
3s
merge-coverage-artifacts
upload-coverage
24s
upload-coverage
Fit to window
Zoom out
Zoom in

Annotations

43 errors and 151 warnings
Test API, headers and no-engine mode
Process completed with exit code 1.
test experimental
Process completed with exit code 1.
Test BaseOnPython execution, Python 3.10"
Process completed with exit code 1.
test-ubuntu (engine native, python 3.10, group_1)
Process completed with exit code 1.
test-windows (engine python, python 3.10, group_1)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine python, python 3.10, group_1)
The operation was canceled.
test-windows (engine dask, python 3.10, group_4)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine dask, python 3.10, group_4)
The operation was canceled.
test-windows (engine ray, python 3.10, group_2)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine ray, python 3.10, group_2)
The operation was canceled.
test-windows (engine dask, python 3.10, group_2)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine dask, python 3.10, group_2)
The operation was canceled.
test-windows (engine ray, python 3.10, group_3)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine ray, python 3.10, group_3)
The operation was canceled.
test-ubuntu (engine python, python 3.10, group_1)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine python, python 3.10, group_1)
The operation was canceled.
test-windows (engine native, python 3.10, group_1)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine native, python 3.10, group_1)
The operation was canceled.
test-windows (engine dask, python 3.10, group_3)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine ray, python 3.10, group_4)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine dask, python 3.10, group_3)
The operation was canceled.
test-ubuntu (engine ray, python 3.10, group_4)
The operation was canceled.
test-ubuntu (engine dask, python 3.10, group_1)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine dask, python 3.10, group_1)
The operation was canceled.
test-ubuntu (engine dask, python 3.10, group_3)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine dask, python 3.10, group_3)
The operation was canceled.
test-ubuntu (engine ray, python 3.10, group_3)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine ray, python 3.10, group_3)
The operation was canceled.
test-windows (engine dask, python 3.10, group_1)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine dask, python 3.10, group_1)
The operation was canceled.
test-ubuntu (engine ray, python 3.10, group_2)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine ray, python 3.10, group_2)
The operation was canceled.
test-ubuntu (engine dask, python 3.10, group_2)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine dask, python 3.10, group_2)
The operation was canceled.
test-ubuntu (engine dask, python 3.10, group_4)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine dask, python 3.10, group_4)
The operation was canceled.
test-ubuntu (engine ray, python 3.10, group_1)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-ubuntu (engine ray, python 3.10, group_1)
The operation was canceled.
test-windows (engine ray, python 3.10, group_1)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine ray, python 3.10, group_1)
The operation was canceled.
test-windows (engine ray, python 3.10, group_4)
The strategy configuration was canceled because "test-all.ubuntu_3_10_native_group_" failed
test-windows (engine ray, python 3.10, group_4)
The operation was canceled.
test-ubuntu (engine unidist mpi, python 3.10)
Process completed with exit code 1.
execution-filter
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
execution-filter
'before' field is missing in event payload - changes will be detected from last commit
test-spreadsheet (engine dask, python 3.10)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-spreadsheet (engine dask, python 3.10)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-spreadsheet (engine dask, python 3.10)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-spreadsheet (engine dask, python 3.10)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-spreadsheet (engine ray, python 3.10)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-spreadsheet (engine ray, python 3.10)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-spreadsheet (engine ray, python 3.10)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-spreadsheet (engine ray, python 3.10)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
Test API, headers and no-engine mode
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
Test API, headers and no-engine mode
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
Test API, headers and no-engine mode
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
Test API, headers and no-engine mode
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test experimental
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test experimental
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test experimental
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test experimental
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
Test BaseOnPython execution, Python 3.10"
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
Test BaseOnPython execution, Python 3.10"
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
Test BaseOnPython execution, Python 3.10"
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
Test BaseOnPython execution, Python 3.10"
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine native, python 3.10, group_1)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine native, python 3.10, group_1)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine native, python 3.10, group_1)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine native, python 3.10, group_1)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine python, python 3.10, group_1)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine python, python 3.10, group_1)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine python, python 3.10, group_1)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine python, python 3.10, group_1)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-windows (engine python, python 3.10, group_1)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine python, python 3.10, group_1)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine python, python 3.10, group_1)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine python, python 3.10, group_1)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine dask, python 3.10, group_4)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine dask, python 3.10, group_4)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine dask, python 3.10, group_4)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine dask, python 3.10, group_4)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-windows (engine dask, python 3.10, group_4)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine dask, python 3.10, group_4)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine dask, python 3.10, group_4)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine dask, python 3.10, group_4)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine ray, python 3.10, group_2)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine ray, python 3.10, group_2)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine ray, python 3.10, group_2)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine ray, python 3.10, group_2)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-windows (engine ray, python 3.10, group_2)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine ray, python 3.10, group_2)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine ray, python 3.10, group_2)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine ray, python 3.10, group_2)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine dask, python 3.10, group_2)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine dask, python 3.10, group_2)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine dask, python 3.10, group_2)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine dask, python 3.10, group_2)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-windows (engine dask, python 3.10, group_2)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine dask, python 3.10, group_2)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine dask, python 3.10, group_2)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine dask, python 3.10, group_2)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine ray, python 3.10, group_3)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine ray, python 3.10, group_3)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine ray, python 3.10, group_3)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine ray, python 3.10, group_3)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-windows (engine ray, python 3.10, group_3)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine ray, python 3.10, group_3)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine ray, python 3.10, group_3)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine ray, python 3.10, group_3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine python, python 3.10, group_1)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine python, python 3.10, group_1)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine python, python 3.10, group_1)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine python, python 3.10, group_1)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine native, python 3.10, group_1)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine native, python 3.10, group_1)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine native, python 3.10, group_1)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine native, python 3.10, group_1)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-windows (engine native, python 3.10, group_1)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine native, python 3.10, group_1)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine native, python 3.10, group_1)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine native, python 3.10, group_1)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine dask, python 3.10, group_3)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine ray, python 3.10, group_4)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine dask, python 3.10, group_3)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine dask, python 3.10, group_3)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-ubuntu (engine ray, python 3.10, group_4)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine dask, python 3.10, group_3)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-ubuntu (engine ray, python 3.10, group_4)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine dask, python 3.10, group_3)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-ubuntu (engine ray, python 3.10, group_4)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine dask, python 3.10, group_3)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine dask, python 3.10, group_3)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine dask, python 3.10, group_3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine dask, python 3.10, group_1)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine dask, python 3.10, group_1)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine dask, python 3.10, group_1)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine dask, python 3.10, group_1)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine dask, python 3.10, group_3)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine dask, python 3.10, group_3)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine dask, python 3.10, group_3)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine dask, python 3.10, group_3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine ray, python 3.10, group_3)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine ray, python 3.10, group_3)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine ray, python 3.10, group_3)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine dask, python 3.10, group_1)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine ray, python 3.10, group_3)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine dask, python 3.10, group_1)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine dask, python 3.10, group_1)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine dask, python 3.10, group_1)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-ubuntu (engine ray, python 3.10, group_2)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine ray, python 3.10, group_2)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine dask, python 3.10, group_1)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine dask, python 3.10, group_1)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-ubuntu (engine ray, python 3.10, group_2)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine ray, python 3.10, group_2)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine dask, python 3.10, group_1)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine dask, python 3.10, group_1)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine dask, python 3.10, group_2)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine dask, python 3.10, group_2)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine dask, python 3.10, group_2)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine dask, python 3.10, group_2)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine dask, python 3.10, group_4)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine dask, python 3.10, group_4)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine dask, python 3.10, group_4)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine dask, python 3.10, group_4)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine ray, python 3.10, group_1)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine ray, python 3.10, group_1)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine ray, python 3.10, group_1)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine ray, python 3.10, group_1)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine ray, python 3.10, group_1)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine ray, python 3.10, group_1)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine ray, python 3.10, group_1)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine ray, python 3.10, group_1)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-windows (engine ray, python 3.10, group_1)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine ray, python 3.10, group_1)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine ray, python 3.10, group_1)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine ray, python 3.10, group_1)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-windows (engine ray, python 3.10, group_4)
Attempt 1 failed. Reason: Child_process exited with error code 1
test-windows (engine ray, python 3.10, group_4)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-windows (engine ray, python 3.10, group_4)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-windows (engine ray, python 3.10, group_4)
warning libmamba [pytest-benchmark-5.2.1-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe
test-windows (engine ray, python 3.10, group_4)
warning libmamba [libgcc-15.2.0-h1383e82_7] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll
test-windows (engine ray, python 3.10, group_4)
warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll
test-windows (engine ray, python 3.10, group_4)
EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.
test-windows (engine ray, python 3.10, group_4)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-windows (engine ray, python 3.10, group_4)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-internals
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-internals
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-internals
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-internals
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
test-ubuntu (engine unidist mpi, python 3.10)
DEPRECATION: Building 'modin-spreadsheet' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'modin-spreadsheet'. Discussion can be found at https://github.com/pypa/pip/issues/6334
test-ubuntu (engine unidist mpi, python 3.10)
warning libmamba You are using 'pip' as an additional package manager. Be aware that packages installed with 'pip' are managed independently from 'conda-forge' channel.
test-ubuntu (engine unidist mpi, python 3.10)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
test-ubuntu (engine unidist mpi, python 3.10)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.

Artifacts

Produced during runtime
Name Size Digest
coverage-data
22.3 KB
sha256:d93806d8242c58efe0987c4302f7573470c89b49a51e40013a6a07b12e74f633