From 20feb1cdbd60a80fa1776d23adef1ad69d879110 Mon Sep 17 00:00:00 2001 From: Abseil Team Date: Wed, 16 Sep 2020 11:55:16 -0700 Subject: Export of internal Abseil changes -- 9214ee309fa224a43eb1621bcf826ab9c86a4cd7 by Abseil Team : Don't keep constructing/destructing `random_device`. It causes an open/close pair on /dev/urandom. This is somewhat expensive on Emscripten, and unnecessary since it is not using the value anyway. PiperOrigin-RevId: 332055452 -- 4931ab77995b946f3ffba8036e0a00927b0d47e6 by Abseil Team : TYPO: Stess->Stress PiperOrigin-RevId: 332010526 -- 95ae1dde505f74dc7fd68447bf27718db223688e by Gennadiy Rozental : Import of CCTZ from GitHub. PiperOrigin-RevId: 332010411 GitOrigin-RevId: 9214ee309fa224a43eb1621bcf826ab9c86a4cd7 Change-Id: I23c5d6aa5aa488370e1b48f37366d3d99448e7ec --- absl/synchronization/mutex_test.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'absl/synchronization') diff --git a/absl/synchronization/mutex_test.cc b/absl/synchronization/mutex_test.cc index 307d0e3f..16fc9058 100644 --- a/absl/synchronization/mutex_test.cc +++ b/absl/synchronization/mutex_test.cc @@ -1102,7 +1102,7 @@ TEST(Mutex, DeadlockDetectorBazelWarning) { // annotation-based static thread-safety analysis is not currently // predicate-aware and cannot tell if the two for-loops that acquire and // release the locks have the same predicates. -TEST(Mutex, DeadlockDetectorStessTest) ABSL_NO_THREAD_SAFETY_ANALYSIS { +TEST(Mutex, DeadlockDetectorStressTest) ABSL_NO_THREAD_SAFETY_ANALYSIS { // Stress test: Here we create a large number of locks and use all of them. // If a deadlock detector keeps a full graph of lock acquisition order, // it will likely be too slow for this test to pass. -- cgit v1.2.3