-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Update to v15.0.0 #1290
Update to v15.0.0 #1290
Conversation
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally. This message was generated by GitHub actions workflow run https://github.com/conda-forge/arrow-cpp-feedstock/actions/runs/7609641679. |
Please add arrow-cpp-feedstock/conda-forge.yml Line 5 in 482b075
|
@@ -3,6 +3,7 @@ azure: | |||
max_parallel: 20 | |||
bot: | |||
abi_migration_branches: | |||
- 14.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JFYI, we'll still need to create that branch; I can do this once we merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already did this as I expect we will merge this PR quite soon(ish).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already did this as I expect we will merge this PR quite soon(ish).
FWIW, let's please only create branches once the PR for the next version gets merged. I've now backported #1292 from main
to 14.x
, but it's easy to forget these sort of details.
Current failures for pandas tests are being tracked here on Arrow: apache/arrow#39732 |
You could add a pin of |
I am quite confused. I force pushed to force a rebuild due to a timeout and now almost all CI jobs are failing. I'll continue investigating what is going on. |
Something is going wrong with getting the libs into place:
Also note that you can restart CI from the checks tab (or after clicking on the details of the CI summary) - just please only click once, and only once all other jobs have finished. The interface between GitHub and azure is buggy and it's possible to unintentionally start several runs simultaneously |
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally. This message was generated by GitHub actions workflow run https://github.com/conda-forge/arrow-cpp-feedstock/actions/runs/7652896641. |
I think the problem is with the migration for libgrpc and libprotobuf. I am trying to re-render locally with
The only thing I can see when doing the migration with the
I am not entirely sure how this migrations work and how |
After some debugging on
before running the re-render. That's probably a bug on |
This is a bit confusing as in this case |
recipe/meta.yaml
Outdated
{% set tests_to_skip = tests_to_skip + " or test_cuda" %} | ||
{% set tests_to_skip = tests_to_skip + " or test_cuda" + " or test_dlpack"%} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is test_dlpack
related to CUDA? It doesn't look like it at first glance.
If not, please put it on a separate line, with a separate comment why that skip is there. If the skip is not absolutely unavoidable (like not having a GPU in CI forces us to skip CUDA tests), it should go below # vvvvvvv TESTS THAT SHOULDN'T HAVE TO BE SKIPPED vvvvvvv
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test does require a GPU, I got a failure about that on CI, @AlenkaF am I right here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The last test from test_dlpack.py
is related to CUDA: test_dlpack_cuda_not_supported. But it should be skipped if CUDA is not installed, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh! so maybe I can try skipping just that test and run the others. Let me try that.
I hadn't found this issue when I wrote efd6784 (forgot to check the closed ones), but it would be good to add a reference to that issue above the Similarly for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sticking through this!
There were a couple of pretty rare & non-obvious issues, normally it's less of an effort. ;-)
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)