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

Allow compilation with any GTest version 1.11+ #13153

Conversation

robertmaynard
Copy link
Contributor

Description

GTest max support for Types was removed in 1.11, so we remove the workarounds in cudf_gtest.

Since we need to support our custom Types and the GTest 1.11+ version rework the type_list_utilities to be generic and not depend on specific traits.

Also corrected the << overloads for GTest printing so that they work with GTest 1.11.

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

GTest max support for `Types` was removed in 1.11, so we remove
the workarounds in cudf_gtest.

Since we need to support our custom `Types` and the GTest 1.11+
version rework the type_list_utilities to be generic and not
depend on specific traits.

Also corrected the `<<` overloads for GTest printing so that
they work with GTest 1.11.
@robertmaynard robertmaynard added bug Something isn't working 3 - Ready for Review Ready for review by team non-breaking Non-breaking change labels Apr 17, 2023
@robertmaynard robertmaynard requested a review from a team as a code owner April 17, 2023 18:02
@robertmaynard robertmaynard requested review from harrism and vuule April 17, 2023 18:02
@github-actions github-actions bot added the libcudf Affects libcudf (C++/CUDA) code. label Apr 17, 2023
@robertmaynard robertmaynard changed the title Allow compilation with any GTest version 1.10+ Allow compilation with any GTest version 1.11+ Apr 17, 2023
Copy link
Contributor

@bdice bdice left a comment

Choose a reason for hiding this comment

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

Changes look fine to me.

Question: Do we need the ostream code for debugging? Seems like a candidate for removal.

@robertmaynard
Copy link
Contributor Author

Question: Do we need the ostream code for debugging? Seems like a candidate for removal.

The ostream code is needed so that we can use the cudf::meanvar type with GTest macro's like EXPECT_EQ and EXPECT_NEAR.

@robertmaynard
Copy link
Contributor Author

/merge

@rapids-bot rapids-bot bot merged commit 1750bff into rapidsai:branch-23.06 Apr 18, 2023
@robertmaynard robertmaynard deleted the bug/support_newer_gtest_versions branch April 18, 2023 14:46
shwina pushed a commit to shwina/cudf that referenced this pull request Apr 18, 2023
GTest max support for `Types` was removed in 1.11, so we remove the workarounds in cudf_gtest.

Since we need to support our custom `Types` and the GTest 1.11+ version rework the type_list_utilities to be generic and not depend on specific traits.

Also corrected the `<<` overloads for GTest printing so that they work with GTest 1.11.

Authors:
  - Robert Maynard (https://github.com/robertmaynard)
  - Vukasin Milovanovic (https://github.com/vuule)

Approvers:
  - Bradley Dice (https://github.com/bdice)
  - Nghia Truong (https://github.com/ttnghia)

URL: rapidsai#13153
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Ready for Review Ready for review by team bug Something isn't working libcudf Affects libcudf (C++/CUDA) code. non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants