Skip to content
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

ARROW-3934: [Gandiva] Only add precompiled tests if ARROW_GANDIVA_BUILD_TESTS #3082

Closed
wants to merge 1 commit into from

Conversation

pcmoritz
Copy link
Contributor

@pcmoritz pcmoritz commented Dec 4, 2018

No description provided.

@wesm
Copy link
Member

wesm commented Dec 4, 2018

Hm, shouldn't this just be if (ARROW_BUILD_TESTS)? I think we should remove the separate flag

@pcmoritz
Copy link
Contributor Author

pcmoritz commented Dec 4, 2018

That's fine with me, I'll change the PR accordingly.

@wesm
Copy link
Member

wesm commented Dec 4, 2018

Sounds good. I think it would be better to use custom targets to control what subcomponents get built (subject to some global options like tests on/off). So we could easily add a custom target so we can write ninja gandiva like we can currently write ninja parquet (or make parquet) and only build the dependencies attached to that target

@pcmoritz
Copy link
Contributor Author

pcmoritz commented Dec 4, 2018

Oh, now I remember why it is done this way: In the Python build matrix entry (the longest one on travis), we build only the arrow tests (for code coverage?) and not the gandiva tests (if we did, the matrix entry would time out). Do you have any suggestion how to handle this? I think it's the only matrix entry where the python gandiva cython wrappers can be reasonably tested.

@pcmoritz
Copy link
Contributor Author

pcmoritz commented Dec 4, 2018

With your suggestion the idea would be to build twice, one with make (tests on) and once with make gandiva (tests off)? Not sure what the impact on build time is in that case...

@wesm
Copy link
Member

wesm commented Dec 4, 2018

Oh right. Let's leave the flag in your patch like it is. We need to https://issues.apache.org/jira/browse/ARROW-3803 and there we can deal with the CMake flags

@pcmoritz
Copy link
Contributor Author

pcmoritz commented Dec 4, 2018

SGTM!

Copy link
Member

@wesm wesm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants