[ci] fix conda env creation in 'regular' CI job (fixes #6282) #6283
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Some of the jobs (Linux regular) are running into mamba-org/mamba#1770, so I'm restoring the conda command. I think it's good to have the env name in case it ever tries to uninstall from base, but probably just having the dask-core will fix it. |
jameslamb
changed the title
jameslamb
requested review from
guolinke,
shiyu1994,
jmoralez and
borchero
as code owners
|
nice @jmoralez !!! I think this fixes it. Thanks so much for working through that. And thanks for the link to that related issue from Anyway, keeping it as Since this is technically my PR, I think you'll need to approve for us to merge it. |
jmoralez
approved these changes
Jan 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6282
We install a package
dask-corebut then in CI later uninstall one calleddask. That might not have been caught before becausedaskwas being pulled in as a transitive dependency of something else (unsure).Anyway, now that it isn't,
conda uninstall daskfails with the error shown in the linked issue.This resolves it by explicitly uninstalling
dask-core.