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
Test against pandas 2.0 #10893
base: main
Are you sure you want to change the base?
Test against pandas 2.0 #10893
Conversation
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 15 files ±0 15 suites ±0 3h 23m 21s ⏱️ + 4m 34s For more details on these failures, see this check. Results for commit 9ea2a49. ± Comparison against base commit 9ba7a97. ♻️ This comment has been updated with latest results. |
There seem to be two genuine failures where tests are green on pandas 1.5/pyarrow 10 and on pandas 2.2/pyarrow 14, but fail on pandas 2.0/pyarrow 12. https://github.com/dask/dask/actions/runs/7973508824/job/21767509851?pr=10893
|
d33c2fc
to
6b491bc
Compare
@phofl how much do we care about these failures? |
I think I care at least a little, but it's not totally clear what is off here, so wouldn't spend that much time investigating |
Now that the 3.12 environment is complete of all its dependencies; we can use the 3.11 one to pin numpy, pandas, and pyarrow in the