Kill the test harness if any test exceeds a timeout. (#16349)
Our tests depend on explicit latching to verify assertion are checked. If a test does not respond for a long time, it has probably encoutered a deadlock. Instead of waiting for the test runner to detect this, apply a very aggresive timeout on a per test basis.
Showing
testing/test_timeout_listener.cc
0 → 100644
testing/test_timeout_listener.h
0 → 100644
想要评论请 注册 或 登录