-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[DO NOT MERGE] Test upstream CI build #8875
Conversation
Looks like we're still installing the same nightly version as yesterday. Actually, if I look back a few days, installing from https://pypi.anaconda.org/scipy-wheels-nightly/simple is giving the same pandas nightly package version. @jorisvandenbossche do you know if there are any known issues around pandas nightly versions not being updated? |
https://pypi.anaconda.org/scipy-wheels-nightly/simple/pandas/ indicates that there are more recent pandas versions, but so not directly an idea why pip is only finding an older one (pandas-1.5.0.dev0+506.g17dda440f9). Locally, I get the same (in a clean env):
|
Thanks @jorisvandenbossche. the nightly builds from main have been failing for a while. didn't realize this till prepped for the release pandas-dev/pandas#45961 (comment) cc @lithomas1 |
it looks like it maybe quite simple to fix... the failing test (preventing the wheels from being upload) is not being skipped by |
should be ok now. |
It looks like I forgot to actually merge #8558 - so it's that and some new groupby failures |
Awesome, thanks for the update @simonjayhawkins! Indeed I'm no longer seeing the segfault 🎉
Rerunning now that #8558 has been merged |
Looks like a lot of the failures are due to pandas-dev/pandas#34998, merged a few days ago |
Oh that is a very nice change! It seems like it will make groupby much more predictable going forward. I can open a PR to address the changes that we need in dask. Unless someone is already on it? |
I'm not aware of anyone working it : ) |
Is there more you wanted to poke at here, or can this be closed? |
Checking to see if our upstream build is passing (xref #8776 (comment))