}

    @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);

	//  - Write quorum not met when upgrading configuration
	//    version is needed, migration is needed etc.
	rquorum := InsufficientReadQuorum{}
	wquorum := InsufficientWriteQuorum{}

	// One of these retriable errors shall be retried.
	return errors.Is(err, errDiskNotFound) ||
		errors.Is(err, errConfigNotFound) ||
		errors.Is(err, context.DeadlineExceeded) ||
		errors.Is(err, errErasureWriteQuorum) ||

- 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;
        }

        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() {

            source.put("category", i < 5 ? 1 : 2); // Use numeric field for reliable filtering
            source.put("value", i);
            client.prepareIndex(INDEX_NAME).setSource(source, XContentType.JSON).execute().actionGet();
        }
        runner.refresh();

        // Use range query for reliable filtering on numeric field

    } 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() {

     * 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

   *    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

  /**