}

    @Test
    @DisplayName("Should check if exception is retriable")
    void testRetriableExceptions() {
        // Test non-retriable errors
        SmbException accessDenied = new SmbException(NtStatus.NT_STATUS_ACCESS_DENIED, false);
        // Note: isRetriable() method does not exist in SmbException
        assertNotNull(accessDenied);

- Fix: add azure disk migration support for CSINode ([#88014](https://github.com/kubernetes/kubernetes/pull/88014), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage]
- Fix: add non-retriable errors in azure clients ([#87941](https://github.com/kubernetes/kubernetes/pull/87941), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider]

- Enable the "Retriable and non-retriable pod failures for jobs" feature into beta. ([#113360](https://github.com/kubernetes/kubernetes/pull/113360), [@mimowo](https://github.com/mimowo))

        private final String description;
        private final ErrorCategory category;
        private final boolean retryable;

        ErrorCode(String description, ErrorCategory category, boolean retryable) {
            this.description = description;
            this.category = category;
            this.retryable = retryable;
        }

        public String getDescription() {
            return description;
        }

- Make the etcd client (used by the API server) retry certain types of errors. The full list of retriable (codes.Unavailable) errors can be found at https://github.com/etcd-io/etcd/blob/main/api/v3rpc/rpctypes/error.go#L72 ([#105069](https://github.com/kubernetes/kubernetes/pull/105069), [@p0lyn0mial](https://github.com/p0lyn0mial))

        assertTrue(exception.getMessage().contains("Disk full"));
    }

    @Test
    @DisplayName("Should have correct retryable flags for error codes")
    void testErrorCodeRetryableFlags() {
        // Retryable errors
        assertTrue(SmbOperationException.ErrorCode.CONNECTION_FAILED.isRetryable());
        assertTrue(SmbOperationException.ErrorCode.CONNECTION_TIMEOUT.isRetryable());

    } finally {
      interruptenator.shutdown();
      Thread.interrupted();
    }
  }

  /**
   * awaitFullGc() is not quite as reliable a way to ensure calling of a specific finalize method as
   * the more direct await* methods, but should be reliable enough in practice to avoid flakiness of
   * this test. (And if it isn't, we'd like to know about it first!)
   */
  public void testAwaitFullGc() {

    } finally {
      interruptenator.shutdown();
      Thread.interrupted();
    }
  }

  /**
   * awaitFullGc() is not quite as reliable a way to ensure calling of a specific finalize method as
   * the more direct await* methods, but should be reliable enough in practice to avoid flakiness of
   * this test. (And if it isn't, we'd like to know about it first!)
   */
  public void testAwaitFullGc() {

   *    has since been closed by the server.
   *  * A client timeout (HTTP 408).
   *  * A authorization challenge (HTTP 401 and 407) that is satisfied by the [Authenticator].
   *  * A retryable server failure (HTTP 503 with a `Retry-After: 0` response header).
   *  * A misdirected request (HTTP 421) on a coalesced connection.
   */
  open fun isOneShot(): Boolean = false

  companion object {

     * opened if it is not and should be closed with {@link #close()} when no longer
     * needed.
     *
     * Closing the context should cancel a pending notify request, but that does not seem to work reliable in all
     * implementations.
     *
     * Changes in between these calls (as long as the file is open) are buffered by the server, so iteratively calling