-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix CI, including mypy "incompatible return type" error in modin/__init__.py:64:12 #7419
Comments
Signed-off-by: sfc-gh-mvashishtha <[email protected]>
mamba-env issues causing other failures. some progress:
I'll keep looking. |
Switching |
A few other things came up in CI on the draft PR:
I am considering removing testing for unidist and MPI. |
This was only needed to speed up the tests, you can safely delete it. Then, if necessary, we can see what has changed and how to return it.
@YarShev do you know what's wrong with unidist in CI? |
@anmyachev because unidist is not being maintained, I'm going to remove CI tests for unidist. cc @devin-petersohn For the record, we did try two different MPI version restrictions, but they didn't work: #7420 (comment) |
The main tests still work, only one with installation via APT does not work. #7420 (comment) |
- Use Miniforge3 instead of Mambaforge in conda-incubator/setup-miniconda action, per conda-incubator/setup-miniconda#383 - Skip test that tries to use Modin with unidist installed via APT. See #7421 for details. - Remove manual conda packaging caching, an optimization which was added to speed up CI but now causes an error complaining that `CONDA_PKGS_DIR` is empty. - Fix some mypy errors in modin/__init__.py
see CI failure here: https://github.com/modin-project/modin/actions/runs/12682127213/job/35347029009
there may be other errors as well
The text was updated successfully, but these errors were encountered: