entries = append(entries, ch)
		}
		out := make(chan metaCacheEntry, 1)
		err := mergeEntryChannels(t.Context(), entries, out, 1)
		if err != nil {
			t.Fatal(err)
		}
		got, ok := <-out
		if !ok {
			t.Fatal("Got no result")
		}

		xl, err := got.xlmeta()
		if err != nil {
			t.Fatal(err)
		}
		if len(xl.versions) != 3 {

"9.1.1 OK"
"9.1.2 OK"
"9.1.3 OK"
"9.1.4 OK"
"9.1.5 OK"
"9.1.6 OK"
"9.2.1 OK"
"9.2.2 OK"
"9.2.3 OK"
"9.2.4 OK"
"9.2.5 OK"
"9.2.6 OK"
"9.3.1 OK"
"9.3.2 OK"
"9.3.3 OK"
"9.3.4 OK"
"9.3.5 OK"
"9.3.6 OK"
"9.3.7 OK"
"9.3.8 OK"
"9.3.9 OK"
"9.4.1 OK"
"9.4.2 OK"
"9.4.3 OK"
"9.4.4 OK"
"9.4.5 OK"
"9.4.6 OK"
"9.4.7 OK"
"9.4.8 OK"
"9.4.9 OK"
"9.5.1 OK"

    /*
     * We always hold the mutex when calling this. TODO(cpovirk): Is that important? Perhaps we need
     * to guarantee that each call to reserveEarliestAvailable, etc. sees a value >= the previous?
     * Also, is it OK that we don't hold the mutex when sleeping?
     */
    protected abstract long readMicros();

    protected abstract void sleepMicrosUninterruptibly(long micros);

        .body("Body")
        .build(),
    )
    newWebSocket()
    clientListener.assertFailure(
      200,
      "Body",
      ProtocolException::class.java,
      "Expected HTTP 101 response but was '200 OK'",
    )
  }

  @Test
  @Throws(IOException::class)
  fun notFound() {
    webServer.enqueue(
      MockResponse
        .Builder()
        .status("HTTP/1.1 404 Not Found")
        .build(),

			mapValue[column] = reflectValue.Interface()
			if valuer, ok := mapValue[column].(driver.Valuer); ok {
				mapValue[column], _ = valuer.Value()
			} else if b, ok := mapValue[column].(sql.RawBytes); ok {
				mapValue[column] = string(b)
			}
		} else {
			mapValue[column] = nil
		}
	}
}

    /*
     * These methods "should" call checkNotNull. However, I'm wary of accidentally introducing
     * anything that might slow down execution on such a hot path. Given that the methods are only
     * package-private, I feel OK with just not testing them for NPE.
     *
     * Note that testing casValue is particularly dangerous because it uses Unsafe under some

    /*
     * These methods "should" call checkNotNull. However, I'm wary of accidentally introducing
     * anything that might slow down execution on such a hot path. Given that the methods are only
     * package-private, I feel OK with just not testing them for NPE.
     *
     * Note that testing casValue is particularly dangerous because it uses Unsafe under some

              <!-- FeatureUtilTest.*ExampleDerivedInterfaceTester, com.google.common.io.*Tester, incidentally FeatureSpecificTestSuiteBuilderTest.MyAbstractTester (but we don't care either way because it's not meant to run on its own but works OK if it does)... but not NullPointerTesterTest, etc. -->
              <exclude>%regex[.*Tester.class]</exclude>
              <!-- Anonymous TestCase subclasses in GeneratedMonitorTest -->

        this.response = response;
    }

    /**
     * Represents the status of an API response.
     */
    public enum Status {
        /** Successful response status. */
        OK(0),
        /** Bad request status indicating client error. */
        BAD_REQUEST(1),
        /** System error status indicating server error. */
        SYSTEM_ERROR(2),

  //
  // See: http://cs.oswego.edu/pipermail/concurrency-interest/2015-January/013800.html
  // For a (long) discussion about this specific issue and the general futility of life.
  //
  // For the time being we are OK with the problem discussed above since it requires a caller to
  // introduce a very specific kind of data-race. And given the other operations performed by these