Search Options

Results per page
Sort
Preferred Languages
Advance

Results 31 - 34 of 34 for Uninterruptibles (0.07 sec)

  1. okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/publicsuffix/BasePublicSuffixList.kt

            initCause(readFailure)
          }
        }
      }
    
      abstract val path: Any
    
      /**
       * Reads the public suffix list treating the operation as uninterruptible. We always want to read
       * the list otherwise we'll be left in a bad state. If the thread was interrupted prior to this
       * operation, it will be re-interrupted after the list is read.
       */
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Mon Jul 28 07:33:49 UTC 2025
    - 3.6K bytes
    - Viewed (0)
  2. guava-tests/test/com/google/common/util/concurrent/TestThread.java

       * at the end of the test, so there is no object state put at risk by stopping the threads
       * abruptly. In other cases, a test may put a thread into an uninterruptible operation
       * intentionally, so there is no other way to clean up these threads. (The better solution,
       * though, would be to run the tests that use TestThread in separate VMs so that their threads
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Thu Dec 11 21:00:51 UTC 2025
    - 11.4K bytes
    - Viewed (0)
  3. guava-tests/test/com/google/common/collect/QueuesTest.java

          fail();
        } catch (InterruptedException expected) {
          // we indeed waited; a slow thread had enough time to interrupt us
        }
      }
    
      // same as above; uninterruptible version
      @SuppressWarnings("ThreadPriorityCheck") // TODO: b/175898629 - Consider onSpinWait.
      private void assertUninterruptibleDrained(BlockingQueue<Object> q) {
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Tue Nov 04 17:24:58 UTC 2025
    - 12.6K bytes
    - Viewed (0)
  4. android/guava-tests/test/com/google/common/util/concurrent/TestThread.java

       * at the end of the test, so there is no object state put at risk by stopping the threads
       * abruptly. In other cases, a test may put a thread into an uninterruptible operation
       * intentionally, so there is no other way to clean up these threads. (The better solution,
       * though, would be to run the tests that use TestThread in separate VMs so that their threads
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Thu Dec 11 21:00:51 UTC 2025
    - 11.4K bytes
    - Viewed (0)
Back to top