-
Notifications
You must be signed in to change notification settings - Fork 9
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
Update to use Googletest v1.10.0 (latest) #8
Conversation
…llout PiperOrigin-RevId: 245430295
Internal Change PiperOrigin-RevId: 245788057
PiperOrigin-RevId: 245798478
Clarify build system support - CMake and automake community supported PiperOrigin-RevId: 245821927
PiperOrigin-RevId: 246550729
Remove special case for protocol buffers. It is no longer needed. PiperOrigin-RevId: 246550795
Print the test output on assertion failure. PiperOrigin-RevId: 247283764
Otherwise the code won't compile if the '&' operater is overloaded and return something that cannot be casted to void *.
PiperOrigin-RevId: 248759825
Adding back section that was lost in merge
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
windows msvc toolchain with werror and wconversion will break if converting long to DWORD.
Cleanup, remove legacy build scripts, googletest only provides Bazel and CMake
PiperOrigin-RevId: 249500162
PiperOrigin-RevId: 249660276
Clarify googler PR policy
As suggested in google#2150.
Add a safety nullptr check to catch the case where the /tmp file used for capturing a stream cannot be created. PiperOrigin-RevId: 250523012
PiperOrigin-RevId: 250620088
Previously this was fused into the source file, but this prevents users of the fused file from using those utilities directly.
I opened a few PRs to fix the warnings: |
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.
This change (plus the fixes in the downstream packages) seem good to me. But I'd like to get an opinion from @wjwwood before we merge.
I think that I did something wrong in updating from googletest and it was hard to tell because the merged in commits were squashed. Now, this PR updates our I've chosen not to squash the commits, since it is what we seem to have done in the past, it makes things clearer, and it should make future updates easier. One other note that might be useful in the future: instead of rebasing, I've chosen to merge these commits when updating from I'll rerun CI. |
Below is CI. Note that I use Build: |
ros2/urdfdom#22 is failing on macOS because the wrong headers are being used (see ros2/urdfdom#23). A better example of 1.10.0 fixing warnings is in ros2/rcl_logging#54 (comment). Note that the most recent version of googletest that passed their CI had two warnings. |
….10.0-2 Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
Here's my latest run of Window's CI: It has two test failures that I see in I'll rerun all of the CI's tonight and if we only see these failures, perhaps we can merge this and the associated PRs in. |
Yeah, I agree that those are flaky tests. So we can ignore those. The changes you have made in this repository also look good. One thing I would like to see is a run of this on Windows Debug and on CentOS. Windows Debug, in particular, has caused a lot of problems in the past, so that would be a good one to see what happens. And while CentOS is not one of our Tier 1 platforms, we do generally try to keep it working, so let's see what happens there. Finally, can you summarize the PRs that are required to get this in? I'd like to get that subset in first before we start enabling warnings elsewhere. |
The required PRs that should be merged in with this PR are
All of the recent CI runs have tested these PRs, too. |
The things that failed in Windows Debug and CentOS are the same that failed in the nightlies, so those are good. I'm happy with this PR, so I'll re-approve and then go look at the other 3 PRs. |
One other thing; once you merge this and the dependent PRs, please make sure to do a release of this package, rcl, rclcpp, and system_tests into Rolling. Otherwise all downstream PR jobs are going to start failing. |
Alright, everyone's happy with the patch, and so am I. Merging on @audrow 's behalf. Thanks! |
I merged in the latest tag of googletest and updated the version number in the
package.xml
.The following PRs are required for this PR: