-
Notifications
You must be signed in to change notification settings - Fork 14
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
Upstream v1.14.0 #106
Upstream v1.14.0 #106
Conversation
Errors like that means you are missing a an include to some resource in vroom upstream. Use a c++ demangler (many online if you search) to find the name, and grep/search for the name in vroom. In simple cases a simple include is enough. In more complicated cases we might need to update the bind layer code in some way. |
Thanks a lot! I fixed the imports. Now I have 5 tests failing and 39 passed. I'll try to solve them by tomorrow
|
Tests are now ok. I had to slightly change the result reported in the |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #106 +/- ##
=======================================
- Coverage 80.0% 79.1% -1.0%
=======================================
Files 29 29
Lines 1572 1628 +56
Branches 114 139 +25
=======================================
+ Hits 1259 1288 +29
- Misses 304 330 +26
- Partials 9 10 +1
Flags with carried forward coverage won't be shown. Click here to find out more. |
Thanks so much for doing this! This is much appriciated. I took a quick look, and I want to test a few things before merging. I am also noticing that macos isn't building on release. I am investigating it now. |
I appologies that this has been just sitting there. As you can see macos isn't building correctly, preventing the build to complete. It is missing an external dep which until now was installed through brew. I can't recreate the bug locally, so the solving this is just a matter of tinkering with deps, paths and/or includes in the CI until I get it right. But until that issue is fixed, merging this will be moot, as we can not release it. |
I also have a mac, I'll try to find a solution |
That is above and beyond! Let me know if you need anything from our side. |
I found two major issues:
|
FYI upstream related ticket VROOM-Project/vroom#1062 |
Main now has fixes that resolves the issue of building on macos. Hopefully now it should be much easier to get to a 1.14 release. Let me know if you have the time to do the last stretch, or if you want me to take over. |
I merged the changes It should be ok now |
Getting there. Do you mind moving Homebrew installs into |
Sure, no problem |
I am trying to solve the issue on macos-intel. As far as I have understood: the build fails because the minimum target for some libraries is OSX 13.6
But if I increase
as the image is based on macos-13. I also tried adding If I add Any idea? We could:
|
Lets try the easy solution and update deploy target to 13.6. |
I just tried updating th target to 13.6 (and then to 14) and made a release(s), but I get the same error unfortunatly. I prefer not reverting as it will prevent pyvroom from having feature parity with upstream vroom. So for now I think further investigation is warrented. Am I to understand that you believe |
* Move flags envs and install * Revert "Update release.yml" This reverts commit 1cd7911. * Update setup.py * Update release.yml * Update release.yml * Update release.yml * Test brew link * Cleaning * Revert "Cleaning" This reverts commit a131e0b. * Update release.yml * Cleaning * Update release.yml * Update release.yml * Fix error on macos-intel * Update release.yml * Cross compile * Update release.yml * Update setup.py * Update * Only build for OSX Arm * Ad universal2 * x86_64 * Update pyproject.toml * Update pyproject.toml * Use [email protected] * Remove [email protected] * Play with openssl * Test * Clean * Try gcc * Update pyproject.toml * Update release.yml * Update release.yml * Update release.yml * Update setup.py * Remove extra instructions * Update pyproject.toml
Using gcc-13 instead of clang solves all the issues. Could you run the workflow now? |
That it does! Looking through the changes I see that you have not only updated to 1.14, but also fixed a couple of bugs along the way. Excellent work Sebastiano! |
The main branch is still failing to build as I forgot to update the main_push.yml file. It should be a quick fix. |
Updating the version of vroom included in pyvroom. I'm creating a draft PR to keep track of the work done:
make develop
)I'm currently getting the following error when running
make test
:I'll try to find a solution...