-
Notifications
You must be signed in to change notification settings - Fork 197
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
Fix various build errors #1152
Fix various build errors #1152
Conversation
Codecov ReportBase: 87.99% // Head: 87.99% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## branch-23.02 #1152 +/- ##
=============================================
Coverage 87.99% 87.99%
=============================================
Files 21 21
Lines 483 483
=============================================
Hits 425 425
Misses 58 58 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
Nice fix, I have been bothered by some of these errors recently as well!
The |
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 the PR!
@@ -32,6 +32,7 @@ function(ConfigureBench) | |||
PRIVATE raft::raft | |||
$<$<BOOL:${ConfigureBench_DIST}>:raft::distance> | |||
$<$<BOOL:${ConfigureBench_NN}>:raft::nn> | |||
GTest::gtest |
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 benchmark shouldn't depend on gtest. I think, we should try to break the offending dependency instead (which is not so trivial).
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.
...Or maybe we could live with the gtest dependency in benchmarks while we solve the problem with the header dependencies? Any thoughts, @cjnolet ?
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.
100% agreed w/ @achirkin here. I was going to type up a similar comment but he beat me to it!
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 benchmark shouldn't depend on gtest. I think, we should try to break the offending dependency instead (which is not so trivial).
My previous comment was in response to this, btw. I don't think we should be crossing the gtest and benchmark dependencies. We should try and pull out the shared bits into a separate header (and maybe try to find a good place in the include/raft/
?) for the shared bits but keep gtest-specific things in test and benchmark-specific things in bench.
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.
I'm also okay opening a github issue about this and keeping the gtest dependency in here for now but adding a comment here that references the issue.
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.
Opened #1153
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.
Given that @cjnolet says we are good with opening an issue about refactoring the GTest dependency required by the benchmarks I am approving the CMake changes.
/merge |
Fix various build errors I encountered as I tried to build RAFT locally on my workstation. (Command used:
./build.sh -g raft-dask pylibraft libraft tests bench --compile-libs
)gtest
as a link dependency of the C++ benchmark suite, to fix the erroralignTo
.alignTo
.areSameAlignOffsets()
, pass the underlying pointers of the mdspan objects. Passing an mdspan toareSameAlignOffsets()
is an error.