diff options
author | Victor Costan <pwnall@chromium.org> | 2018-02-23 14:55:25 -0800 |
---|---|---|
committer | Victor Costan <pwnall@chromium.org> | 2018-02-27 07:50:03 -0800 |
commit | 84ec2e0365d791e4ebc7ec249f09078fb5ab6caa (patch) | |
tree | c408ccc78b5a07196a10ccf24dda2d65ba1b57a7 /googlemock | |
parent | ac34e6c950925df7165e626becd3f9d64dcd584b (diff) | |
download | googletest-84ec2e0365d791e4ebc7ec249f09078fb5ab6caa.tar.gz googletest-84ec2e0365d791e4ebc7ec249f09078fb5ab6caa.tar.bz2 googletest-84ec2e0365d791e4ebc7ec249f09078fb5ab6caa.zip |
Switch default death test style back to "fast".
Google Test has recently (02/09/2018) switched the default death test
style from "fast" to "threadsafe" in
https://github.com/google/googletest/commit/ec7faa943d7817c81ce7bdf71a21ebc9244dc8de
Threadsafe death tests have been used internally for a while, and are
proven to be a better default.
However, adopting this better default can be challenging for large
projects with a significant investment in custom infrastructure built on
top of Google Test. The same custom infrastructure can make it difficult
for large projects to switch back to the old default by passing in
--gtest_death_test_style=fast.
For the reasons above, the default switch is considered too disruptive,
and this CL reverts it. This CL also introduces the
GTEST_DEFAULT_DEATH_TEST_STYLE preprocesor macro, which replaces the
hard-coded default. The macro can be defined in
gtest/internal/custom/gtest-port.h by projects that are ready to migrate
to thread-safe death tests.
Diffstat (limited to 'googlemock')
0 files changed, 0 insertions, 0 deletions