while (computedCount.get() < nThreads) {
      Thread.yield();
    }
    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.)

            // Given
            byte[] buffer = new byte[60];
            SMBUtil.writeInt2(60, buffer, 0);

            // Write negative times (as they would appear in the buffer)
            SMBUtil.writeInt8(-1L, buffer, 8);
            SMBUtil.writeInt8(-1000L, buffer, 16);
            SMBUtil.writeInt8(-2000L, buffer, 24);

    assertThat(networkAsMutableNetwork.removeNode(N1)).isTrue();

    // The choice of the size() method to call here is arbitrary.  We assume that if any of the Set
    // methods executes the validation check, they all will, and thus we only need to test one of
    // them to ensure that the validation check happens and has the expected behavior.
    assertNodeRemovedFromGraphErrorMessage(

   * @param b the second {@code short} to compare
   * @return a negative value if {@code a} is less than {@code b}; a positive value if {@code a} is
   *     greater than {@code b}; or zero if they are equal
   */
  @InlineMe(replacement = "Short.compare(a, b)")
  public static int compare(short a, short b) {
    return Short.compare(a, b);
  }

  /**

   * @param b the second {@code short} to compare
   * @return a negative value if {@code a} is less than {@code b}; a positive value if {@code a} is
   *     greater than {@code b}; or zero if they are equal
   */
  @InlineMe(replacement = "Short.compare(a, b)")
  public static int compare(short a, short b) {
    return Short.compare(a, b);
  }

  /**

The documentation for each of these specifies the guarantees it
makes concerning synchronization.
</p>

<p>
Other packages that provide synchronization abstractions
should document the guarantees they make too.
</p>


<h2 id="badsync">Incorrect synchronization</h2>

<p>
Programs with races are incorrect and
can exhibit non-sequentially consistent executions.

http://%zz%66%a.com

# If we get an invalid character that has been escaped.
http://%25
http://hello%00

# Escaped numbers should be treated like IP addresses if they are.
# No special handling for IPv4 or IPv4-like URLs
http://%30%78%63%30%2e%30%32%35%30.01  s:http p:/ h:192.168.0.1
http://%30%78%63%30%2e%30%32%35%30.01%2e  s:http p:/ h:0xc0.0250.01.
http://192.168.0.257

    // This tests to ensure that:
    // 1. service times are accurate when the service is started by the manager
    // 2. service times are recorded when the service is not started by the manager (but they may
    // not be accurate).
    Service b =
        new NoOpDelayedService(353) {
          @Override
          protected void doStart() {
            super.doStart();

  // TODO(lukes): Investigate using a @Contended annotation on these fields once one is available.

  /*
   * The following fields are package-private, even though we intend never to use them outside this
   * file. If they were instead private, then we wouldn't be able to access them reflectively from
   * within VarHandleAtomicHelper and AtomicReferenceFieldUpdaterAtomicHelper.
   *

                 * BCAST, Node Status) we need to augment the hashcode generated
                 * for the addresses hostname or failed lookups for one type will
                 * be cached and cause other types to fail even though they may
                 * not be the authority for the name. For example, if a WINS lookup
                 * for FOO fails and caches unknownAddress for FOO, a subsequent