- Fixed a regression that could incorrectly reject pods with `OutOfCpu` errors if they were rapidly scheduled after other pods were reported as complete in the API. The Kubelet now waits to report the phase of a pod as terminal in the API until all running containers are guaranteed to have stopped and no new containers can be started.  Short-lived pods may take slightly longer (~1s) to report Succeeded or Failed after this change....

                      () -> {
                        // WAIT #1
                        barrier.await(1, SECONDS);

                        // WAIT #2
                        barrier.await(1, SECONDS);
                        assertTrue(executor.isShutdown());
                        assertFalse(executor.isTerminated());

                        // WAIT #3
                        barrier.await(1, SECONDS);

* `kubectl wait` is a new command that allows waiting for one or more resources to be deleted or to reach a specific condition. It adds a `kubectl wait --for=[delete|condition=condition-name] resource/string` command. ([#64034](https://github.com/kubernetes/kubernetes/pull/64034), [@deads2k](https://github.com/deads2k))

        // Should still not be expired
        assertFalse(auth.isExpired());

        // Wait for original TTL to pass
        Thread.sleep(600);

        // Should still not be expired because we reset
        assertFalse(auth.isExpired());

        // Wait for the full TTL since reset
        Thread.sleep(500);

        // Now it should be expired

    runLatch.await();
    assertEquals(1, listenerLatch.getCount());
    assertFalse(task.isDone());
    assertFalse(task.isCancelled());

    // Finish the task by unblocking the task latch.  Then wait for the
    // listener to be called by blocking on the listener latch.
    taskLatch.countDown();
    assertEquals(25, task.get().intValue());
    assertTrue(listenerLatch.await(5, SECONDS));

     * If someone called cancel(true), it is possible that the interrupted bit hasn't been set yet.
     * Wait for the interrupting thread to set DONE. (See interruptTask().) We want to wait so that
     * the interrupting thread doesn't interrupt the _next_ thing to run on this thread.
     *
     * Note: We don't reset the interrupted bit, just wait for it to be set. If this is a thread

                      () -> {
                        // WAIT #1
                        barrier.await(1, SECONDS);

                        // WAIT #2
                        barrier.await(1, SECONDS);
                        assertTrue(executor.isShutdown());
                        assertFalse(executor.isTerminated());

                        // WAIT #3
                        barrier.await(1, SECONDS);

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.testcontainers.containers.GenericContainer;
import org.testcontainers.containers.output.Slf4jLogConsumer;
import org.testcontainers.containers.wait.strategy.Wait;
import org.testcontainers.junit.jupiter.Container;
import org.testcontainers.junit.jupiter.Testcontainers;
import org.testcontainers.utility.MountableFile;

import jcifs.CIFSContext;
import jcifs.Configuration;

    }
    return new ListenableFutureAdapter<>(future, executor);
  }

  /**
   * An adapter to turn a {@link Future} into a {@link ListenableFuture}. This will wait on the
   * future to finish, and when it completes, run the listeners. This implementation will wait on
   * the source future indefinitely, so if the source future never completes, the adapter will never
   * complete either.
   *

                executor.shutdownNow();
            }
        }

        long elapsed = (System.nanoTime() - time) / 1000000;
        long wait = waittime * (numTasks - 1);
        assertTrue(elapsed + " >= " + wait, elapsed + 1L >= wait);
    }

    /**
     * Test that different hosts can be accessed concurrently without delay
     */
    public void test_multipleHosts_concurrent() {