Mike Hommey f238dce0bd Bug 1419196 - Use the "threadsafe" variant of gtest death tests. r=ted ... Because the default "fast" variant uses fork() on !windows, death tests are dangerous, as they themselves say. There are race conditions involving locks that lead to dead locks in the death test process while disabling the crash reporter (currently, but this could happen for different code, even the tested code itself). See https://bugzilla.mozilla.org/show_bug.cgi?id=1419196#c7 for details. Using the "threadsafe" variant creates new processes for each death test. This is notably slower, but can't dead-lock because of some random lock being held by some random other thread at the moment fork occurred. --HG-- extra : rebase_source : 56bf678bc9a6588751520549d57db7293134e1f8		2017-11-24 14:22:20 +09:00
..
benchmark	Bug 1396208 - For benchmarking, add a black box function that is opaque to the optimizer. r=froydnj	2017-10-10 09:48:26 +03:00
gmock	Bug 1343557 - Update gtest and gmock to 1.7.0; r=ted.mielczarek	2017-03-02 08:59:50 -05:00
gtest	Bug 1406687 Pass return values from fwrite to Unused to silence the warn-unused-result warning r=njn	2017-10-09 15:01:48 -05:00
mozilla	Bug 1402519 - Remove MOZ_CRASHREPORTER directives from testing; r=ted.mielczarek	2017-10-10 15:22:56 +02:00
Makefile.in	…
MozGtestFriend.h	…
bench.py	Bug 1394604 - Avoid direct path to python3 in bench script. r=froydnj	2017-08-30 10:34:00 -04:00
moz.build	Bug 1396208 - For benchmarking, add a black box function that is opaque to the optimizer. r=froydnj	2017-10-10 09:48:26 +03:00
rungtests.py	Bug 1419196 - Use the "threadsafe" variant of gtest death tests. r=ted	2017-11-24 14:22:20 +09:00