Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 4 of 4 for saw (0.01 seconds)

  1. android/guava-tests/test/com/google/common/cache/CacheBuilderTest.java

        }
        cache.invalidateAll();
        tasksFinished.await();
    
        // Check all of the removal notifications we received: they should have had correctly-associated
        // keys and values. (An earlier bug saw removal notifications for in-progress computations,
        // which had real keys with null values.)
        Map<String, String> removalNotifications = new HashMap<>();
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Wed Mar 18 18:06:14 GMT 2026
    - 25.7K bytes
    - Click Count (0)
  2. guava-tests/test/com/google/common/cache/CacheBuilderTest.java

        }
        cache.invalidateAll();
        tasksFinished.await();
    
        // Check all of the removal notifications we received: they should have had correctly-associated
        // keys and values. (An earlier bug saw removal notifications for in-progress computations,
        // which had real keys with null values.)
        Map<String, String> removalNotifications = new HashMap<>();
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Wed Mar 18 18:06:14 GMT 2026
    - 25.6K bytes
    - Click Count (0)
  3. android/guava-tests/test/com/google/common/util/concurrent/FuturesTest.java

       * to hang (possibly too quickly, but too-quick failures should be very unlikely, given that we
       * used to bail after 20ms during the expected-successful tests, and there we saw a failure rate
       * of ~1/5000, meaning that the other thread's get() call nearly always completes within 20ms if
       * it's going to complete at all).
       *
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Mon Mar 16 22:45:21 GMT 2026
    - 134K bytes
    - Click Count (0)
  4. guava-tests/test/com/google/common/util/concurrent/FuturesTest.java

       * to hang (possibly too quickly, but too-quick failures should be very unlikely, given that we
       * used to bail after 20ms during the expected-successful tests, and there we saw a failure rate
       * of ~1/5000, meaning that the other thread's get() call nearly always completes within 20ms if
       * it's going to complete at all).
       *
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Mon Mar 16 22:45:21 GMT 2026
    - 134K bytes
    - Click Count (0)
Back to Top