Skip to content
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 failing tests #416

Merged
merged 5 commits into from
Oct 31, 2023
Merged

Fix CI failing tests #416

merged 5 commits into from
Oct 31, 2023

Conversation

lukaszo
Copy link
Contributor

@lukaszo lukaszo commented Oct 18, 2023

It looks like CI currently fails because of three reasons:

  1. pytest-asyncio defaults now to the strict mode
    There are two ways to fix it. Switch back to using auto mode or replace all @pytest.fixture with @pytest_asyncio.fixture
    In this PR I've used the first option. If you prefer the second option, I will update the PR.
  2. dask dropped support for python3.8
    When creating conda env for 3.8 it fails with the following error message:
    ERROR: Package 'dask' requires a different Python: 3.8.18 not in '>=3.9'
    To fix it, I've removed python3.8 and updated all examples to use 3.9
  3. Outdated Read The Docs config.
    Updated.

@lukaszo lukaszo force-pushed the python_versions branch 5 times, most recently from ced80bb to e3e4709 Compare October 18, 2023 23:35
@lukaszo
Copy link
Contributor Author

lukaszo commented Oct 19, 2023

Even though I've removed it, it looks like it's still waiting for the 3.8 test to finish. Maybe it's some kind of protection as I'm not a member of the team, but I'm modifying the CI 🤷‍♂️

@lukaszo
Copy link
Contributor Author

lukaszo commented Oct 19, 2023

Ok, it seems that the test for 3.8 is marked in Require status checks to pass before merging list in the repo settings.

@lukaszo
Copy link
Contributor Author

lukaszo commented Oct 26, 2023

Hi @jacobtomlinson Will you have a time to check this out?

Copy link
Member

@jacobtomlinson jacobtomlinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay in reviewing here. This looks great. At some point I would like to explore dropping pytest-asyncio in favour of pytest-anyio with just the asycnio backend as we have done in other parts of Dask, but in the meantime this gets things going.

I'll change the branch protection rules accordingly.

@jacobtomlinson jacobtomlinson merged commit afe8e56 into dask:main Oct 31, 2023
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants