forked from google/googletest
-
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 gtest 1.14 #27
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PiperOrigin-RevId: 481680362 Change-Id: I87b2b71427a8ad2603f5445d6ef794c3fa84746e
PiperOrigin-RevId: 481734961 Change-Id: I629dc1ca3b10bf5fc6afc179b651a09081f5c919
PiperOrigin-RevId: 481765573 Change-Id: I1ba829c3cbf364a51d3ba383ee3b474c0e109578
…h::IsRootDirectory() in GoogleTest Fixes: google#3025 PiperOrigin-RevId: 481932601 Change-Id: I90fcb5b3d189aea79a0fd18735bad038b3511270
PiperOrigin-RevId: 482101793 Change-Id: I1bd140fd6a325f573c8a0c464e4dccd4acd0d0a3
PiperOrigin-RevId: 482287697 Change-Id: I1179a1570cd64fcb156bda26e5c779b876c51742
Signed-off-by: Denis Hananein <[email protected]>
Signed-off-by: Denis Hananein <[email protected]>
Signed-off-by: Denis Hananein <[email protected]>
This aims to avoid confusion as to what kinds of computations are valid inside a parameter generator expression, calling out flags as a supported use case. PiperOrigin-RevId: 483397027 Change-Id: I2d036fae95120d617f30a5566ea7498ce1f9bfb6
Commit hashes reflect GoogleTest's live-at-head stance. Credits to @shinfd. Fixes google#4000 PiperOrigin-RevId: 483655943 Change-Id: Ieeb162859348dbe3657e18f283bac81412f2585d
PiperOrigin-RevId: 483683590 Change-Id: Id22de3a22018324e5c1e21e262ac5e027a83bf3e
PiperOrigin-RevId: 485895339 Change-Id: I09b0f535941531ef7bcb74593d385891d56b3e32
PiperOrigin-RevId: 486316328 Change-Id: I91d5d5ba1aaf4a4ab14019c8963e7fe181722f95
PiperOrigin-RevId: 486685761 Change-Id: I164d2646e65670d341dbf437ee571953c456677a
Fixes: google#4048 PiperOrigin-RevId: 486951561 Change-Id: I4fae101b5ac5ed4f46c32aba8c36519e1f784db1
PiperOrigin-RevId: 487516335 Change-Id: Ib475750586fc7e6ab01729f65253e3a86916b994
Signed-off-by: Denis Hananein <[email protected]>
…tory where ancillary data files can be found. PiperOrigin-RevId: 487896836 Change-Id: Ie6b1ba734e900fa33872b63090879ee6efe33411
PiperOrigin-RevId: 488456139 Change-Id: I648f3d2c6affadfea27214a6a22cacc576971cef
PiperOrigin-RevId: 488463135 Change-Id: I4180d766dabbe438210904e743e6e963122540f5
Fixes: google#4054 PiperOrigin-RevId: 488721587 Change-Id: I8742d8475376635c83edcf524796a6107042e89b
To make debug output readable, we still use the faster 6-digit precision sometimes, but only if it will round-trip. This way, when a test fails due to a very small difference in floating-point numbers, users will have enough digits to see the difference. PiperOrigin-RevId: 488958311 Change-Id: Ibcac43f48a97006d89217530c69386cc4fa2735c
PiperOrigin-RevId: 490057649 Change-Id: Ia788d55cfbc576e841064b8e907f8671cc46f3bf
PiperOrigin-RevId: 490601453 Change-Id: I733b2ed8740b1c809dddb166a42993b869198469
…at trigger via `MOCK_METHOD()` and `EXPECT_THAT()` macros. Fixes: google#4052, google#4055 PiperOrigin-RevId: 491647393 Change-Id: I8e2ad838156fa8c7e9dccd1740af797e694992b6
…nterface. MatcherDescriberInterface specifies that DescribeTo "should print a verb phrase", but "size ..." is not a verb phrase. Currently, ElementsAre(SizeIs(9)) is described as "has 1 element that size is equal to 9". With this change, it will be described as "has 1 element that has a size that is equal to 9". PiperOrigin-RevId: 492022324 Change-Id: I4083335f2419462464957521c1e033643b53b763
…nged ordering. PiperOrigin-RevId: 546373360 Change-Id: I2538b45d8c7710592071cc352da6771480c324e6
PiperOrigin-RevId: 547250378 Change-Id: I084c30e45f331cb296535822923da1cb7e848e11
PiperOrigin-RevId: 549006105 Change-Id: Ifbe2bf57e10df4c71e51dbfaf1687f4f621f5106
PiperOrigin-RevId: 549039222 Change-Id: I96bea310beede5ba0ed6160155251ffd9d7a2103
PiperOrigin-RevId: 549456180 Change-Id: I10862e6de981087a5c590cccf6152255e9a176a0
Fixes google#4314 PiperOrigin-RevId: 549986457 Change-Id: Iff74f02ab1c106696f288540e9c623d56b76e3f7
PiperOrigin-RevId: 550585850 Change-Id: I727f74aeb6f1da5bbbf5a5f49f06c4cfea40a73b
…ages. Right now, gtest documentation uses different #include syntax. The quickstart pages (e.g., http://google.github.io/googletest/quickstart-bazel.html#create-and-run-a-binary) are checked in with `#include <gtest/gtest.h>` However, other documentation (such as the primer) uses `#include "gtest/gtest.h"` (e.g., https://google.github.io/googletest/primer.html#writing-the-main-function). PiperOrigin-RevId: 551878641 Change-Id: Iab93cc1da3ef4870a07b624071b75d6e9d3568c1
PiperOrigin-RevId: 552577282 Change-Id: I2b4d20d155ad5746e36711c039293d5c996a332e
PiperOrigin-RevId: 552912819 Change-Id: If1b6278f7fe5a8fc41fc3bc390356a94387d0091
This allows types that provide an AbslStringify definition to be streamed into GoogleTest macros. PiperOrigin-RevId: 552914482 Change-Id: I5fb386980d4d24873f95f0a8ef83067a6a3c86ac
It appears to have been unintentionally left out PiperOrigin-RevId: 553141410 Change-Id: I8adac55a3df0ec12d6fe03446f71858fc702e178
PiperOrigin-RevId: 553150809 Change-Id: I10d19a45a85c5f63a5e65dc322413307116e1c25
PiperOrigin-RevId: 553152072 Change-Id: I0bfbb2da6b3902fc3e41a8e1c4aacb291ffdd098
Signed-off-by: Chris Lalancette <[email protected]>
I did a local build with no issues, LGTM. Note: I can't review or mark the approval since I'm not assigned. |
With the fixes from osrf/osrf_testing_tools_cpp#84 in place, here is another shot at CI: |
ahcorde
approved these changes
Feb 8, 2024
mjcarroll
approved these changes
Feb 9, 2024
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.
+24,365/-27,822
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This matches the version that will be in Ubuntu 24.04, and should resolve some CMake warnings when building on that platform.
@marcoag please take a look at this and osrf/osrf_testing_tools_cpp#84 when you get a chance.