-
Notifications
You must be signed in to change notification settings - Fork 84
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 error so latest version of googletest can be used #954
Conversation
@brtietz I think the errors here in the CI are because the older version of gtest is still being used, while these new changes are meant for compatibility with the latest version. |
I was able to build successfully on Windows. The errors on Mac and Linux look different now. Is it better to remove the copy & assign macro or update these additional tests?
|
I don't think we should remove the macro as it looks to be needed for the intended functionality, which is to allow categorization of the tests in the Visual Studio Test Explorer. Part of my recent change was to add the 'int' return type on line 39 of vs_google_test_explorer_namespace.h . However, this seems to break the code on Mac and Linux. @sjanzou Can I please take you up on your offer to test this on Mac and Linux? And maybe try different return types or selectively set the return type via something like: |
@Matthew-Boyd , thanks for the details - I am running locally on CentOS7 and MacOS 13 and will update here. |
@Matthew-Boyd, the #if worked fine on MacOS with the "int" removed using the old googletest. However, for the new googletest, the gtest-port.h line 270 requires c++14 We will definitely not be able to support that when building on CentOS7. So, I am not sure if there is a path forward if we need to support the Eagle HPC configuration and the latest googletest. The latet commit on this branch updated all workflows and CMakelist.txt to C++14 for testing. |
@sjanzou Thanks a lot for looking into this and finding the limitation. It looks like the options are to keep googletest pinned at that previous version or remove this categorization. I'm fine with either, and I may be the only one who cares about this feature. @brtietz , do you want to make the decision? If we're not keeping it pinned, I'll update the categorized tests so there's no errors. |
@Matthew-Boyd I put this on the meeting agenda for discussion. Some things I'm thinking about:
|
Revisit in July '23 after we upgrade to C++14 |
Fix error in googletest macro so that the latest version of googletest can be used.
@brtietz I think the installation instructions can be updated now to use the latest gtest version
Closes #806