-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Tests fail with pytest 8.1 when a data
dir exists
#2993
Comments
It looks like pinning Would be nice to not pin pytest. |
@flying-sheep does anndata need to have a pytest minimum bound of |
What happens is
I assume that some of the attempts to fix our doctest woes in Pytest 8.1 led to this bug being introduced in Pytest 8.1. But I’d like to figure out what exactly causes that bug before we do anything. PS: Of course things like this are exactly why we switched anndata to a |
@flying-sheep do you want to use this issue to investigate why this doesn't work with pytest 8.1, or track that in a new issue for unpinning it? If you want to track it here, feel free to edit the title |
data
dir exists
Done. I think the difference between CI and local is that locally, the |
What's your proposed solution? It seems like that should be fine, so I'm imagining something needs to change in pytest? |
Still no clue: pytest-dev/pytest#12194 (comment) I haven’t been able to create a minimal reproducer yet. The problem is that the wrong module gets returned by a |
This is fixed in pytest-dev/pytest#12169. Let’s wait for the pytest release, and then bump the min pytest version. |
Does pytest track their releases somewhere public? Curious what the timeline is here |
Here? I think if we ask nicely they’ll make one soon |
I mean like milestones or projects for upcoming releases. It look like the change that fixes the issue got marked as an improvement, so we'd be waiting on 8.2. |
I asked: pytest-dev/pytest#12169 (comment) |
There’s an 8.2 release planning issue now: pytest-dev/pytest#12213 |
First reported by @lazappi, but now confirmed by me.
Tests error during collection for a fresh dev install.
First everything fails since
dask-expr
isn't installed. This must be someone upstream pinning dask, but is easily solvable by adding dask-expr to the environment.Failures
Now we get a ton of failures due to a failure to import test dataset helpers
Pinning
pytest<8
seems to resolve the issue.@flying-sheep any ideas? Any idea why CI is working with pytest 8.1.1 while we get failures locally?
Environment info
My environments are both using ubuntu
My working env
My failing env
Luke's environment: MacOS Ventura 13.4.1. Intel MacBook pro
Luke's failing env
TODO:
The text was updated successfully, but these errors were encountered: