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
..
dumbmake
mozbuild	Bug 1419196 - Use the "threadsafe" variant of gtest death tests. r=ted	2017-11-24 14:22:20 +09:00
mozpack	Backed out changeset 6f0e650b0e53 (bug 1416465) on request from nalexander for many busted build environments. r=backout a=backout	2017-11-16 18:41:24 +02:00
setup.py
TODO