-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
Nightly Builds #30730
Comments
looks like the nightly wheel build has been failing https://travis-ci.org/MacPython/pandas-wheels/builds i don’t think i get status emails on this any more cc @pandas-core if someone can look |
@pandas-dev/pandas-core |
I can have a look, but I wasn't aware we had this. If it's not in our CI, who is maintaining those builds? Probably I'm missing something, but if the idea is providing wheels, shouldn't it be better to generate them from our own builds? I think our CI is already too complex to also have to maintain builds elsewhere. |
wheel building is a separate animal and non trivial these are documented as part of the release process i suppose you could do the nightly builds as github actions |
Thanks for the info, will check the release docs. |
I was also going to take a look at the wheel building stuff on Tuesday in preparation for the RC. |
ref pandas-dev/pandas-release#20 I do think switching over to Actions would be possible; I've done something similar for another project https://github.com/innobi/pantab/pull/37/files sans the manylinux piece |
Should be fixed by MacPython/pandas-wheels#68 |
Until 2019-11-02, https://7933911d6844c6c53a7d-47bd50c35cd79bd838daf386af554a83.ssl.cf2.rackcdn.com/ contains nightly builds of pandas for different platforms. Is there any chance that this will be continued? I am asking because nightly testing is very helpful for some downstream artifacts to discover unintentional breaking chances or regressions before a new pandas version gets released. Building pandas from source on CI takes very long though, up to a duration where it gets kinda unpractical for downstream projects.
The text was updated successfully, but these errors were encountered: