-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[CI][Conda] Nightly CI jobs aren't maintained #14828
Comments
I've been planning to update them as soon as conda-forge/arrow-cpp-feedstock#875 is merged, but that PR took quite a while for various reasons (needs to cross-compile for aarch/ppc, which didn't work in conjunction with CUDA; there's a path to make this work but I'm not going to block the PR on that; also, bunch of tests failed and there were some segfaults, but I received essentially no response to many pings about what to do with them, so for now I'll ignore them). After that update the CI should run fine IMO, and it should be easy to update after that as well. The test failures and segfaults I mentioned IMO make running things in CI here worthwhile, as another angle through which to stresstest the code (before the PR linked above, the conda-forge feedstock didn't run the test suite; now it does). However I can't speak for the jobs that also include R. Haven't looked at those, so far only @xhochy did AFAIU. |
Thanks for sharing the current status. Sorry for not replying to segfaults... I couldn't follow conda-forge/arrow-cpp-feedstock#875 because it's too large for me. |
It doesn't bother me at all. I didn't want to spam people with issues, and thought it would be easier to ask specific questions (e.g. about the LLVM usage), but if people prefer issues here that's not a problem for me. |
While preparing a PR, I just saw that a3ef64b broadly undid several necessary infrastructure changes in CC @assignUser, please be more careful next time |
@h-vetinari Oh 😱 seems like I picked the wrong chunk and it slipped through the review. Sorry |
Oh, sorry. I missed these changes on merging... |
Synching after conda-forge/arrow-cpp-feedstock#875, which does quite a lot of things, see this [summary](conda-forge/arrow-cpp-feedstock#875 (review)). I'm not keeping the commit history here, but it might be instructive to check the commits there to see why certain changes came about. It also fixes the CI that was broken by a3ef64b (undoing the changes of #14102 in `tasks.yml`). Finally, it adapts to conda making a long-planned [switch](conda-forge/conda-forge.github.io#1586) w.r.t. to the format / extension of the artefacts it produces. I'm very likely going to need some help (or at least pointers) for the R-stuff. CC @ xhochy (for context, I never got a response to conda-forge/r-arrow-feedstock#55, but I'll open a PR to build against libarrow 10). Once this is done, I can open issues to tackle the tests that shouldn't be failing, resp. the segfaults on PPC resp. in conjunction with `sparse`. * Closes: #14828 Authored-by: H. Vetinari <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
Nightly CI jobs for Conda were fixed by @h-vetinari and @xhochy in GH-14102 but most nightly CI jobs are failing again this past month.
Can we maintain them? If we can't maintain them, can we remove them? Are they useful to maintain https://github.com/conda-forge/arrow-cpp-feedstock ?
http://crossbow.voltrondata.com/
Component(s)
Continuous Integration, Packaging
The text was updated successfully, but these errors were encountered: