Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 2.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

The operation was canceled.

The strategy configuration was canceled because "test-all.ubuntu_3_10_ray_group_2" failed

The operation was canceled.

Process completed with exit code 1.

The job has exceeded the maximum execution time of 6h0m0s

The operation was canceled.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5, dorny/paths-filter@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The `python-version` input is not set. The version of Python currently in `PATH` will be used.

'before' field is missing in event payload - changes will be detected from last commit

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba draining failed An existing connection was forcibly closed by the remote host.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3, nick-fields/retry@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3, nick-fields/retry@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

warning libmamba [pytest-benchmark-5.2.3-pyhd8ed1ab_0] The following files were already present in the environment: - scripts\py.exe

warning libmamba [libgcc-16.1.0-h110b43a_1] The following files were already present in the environment: - Library\bin\libgcc_s_seh-1.dll

warning libmamba [libwinpthread-12.0.0.r4.gg4f2fc60ca-h57928b3_10] The following files were already present in the environment: - Library\bin\libwinpthread-1.dll

ERROR: 'conda activate "modin"' exited with code 1.

EnvironmentNameNotFound: Could not find conda environment: modin You can list all discoverable environments with `conda info --envs`.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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'.

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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.

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'.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, conda-incubator/setup-miniconda@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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.

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'.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact/merge@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/