| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Fix bazel issue
PiperOrigin-RevId: 223829127
|
|
|
|
|
|
| |
Fix bazel issue
PiperOrigin-RevId: 223823930
|
|
|
|
|
|
|
|
| |
Improve Bazel build files.
New target gtest_prod allows access to the FRIEND_TEST macro without depending on the entirety of GTest in production executables. Additionally, duplicate config_setting rules were removed and formatting was adjusted.
PiperOrigin-RevId: 220279205
|
|
|
|
|
|
| |
Internal Change
PiperOrigin-RevId: 215236414
|
|
|
|
|
|
| |
Add myself to the authors table.
PiperOrigin-RevId: 214822035
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change adds the ability to generate stacktraces in Google Test on
both failures of assertions/expectations and on crashes. The
stacktrace support is conditionally available only when using Abseil
with Google Test.
To use this support, run the test under Bazel with a command like this:
bazel test --define absl=1 --test_env=GTEST_INSTALL_FAILURE_SIGNAL_HANDLER=1 //path/to/your:test
The "--define absl=1" part enables stacktraces on assertion/expectation
failures.
The "--test_env=GTEST_INSTALL_FAILURE_SIGNAL_HANDLER=1" part enables
the signal handler that logs a stacktrace in the event of a crash
(this also requires the "--define absl=1" part). This is not the
default since it may interfere with existing tests.
|
| |
|
| |
|
|
|
|
| |
and x64_windows_msvc
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|