Retries

This is the logic that kicks in if preventive retries facilitated by flakiness configuration have failed.

caution

Retries from this configuration are added in-flight, i.e. after the tests were actually executed, hence there is no way to parallelize test run to achieve maximum utilization of devices. This will significantly affect the performance of the test run.

No retries

As the name implies, no retries are done. This is the default mode.

Marathonfile

retryStrategy:
  type: "no-retry"

Kotlin DSL

marathon {
  retryStrategy {}
}

Groovy DSL

marathon {
  retryStrategy {}
}

Fixed quota retry strategy

Parameter totalAllowedRetryQuota below specifies how many retries at all (for all the tests is total) are allowed.

Parameter retryPerTestQuota controls how many retries can be done for each test individually.

Marathonfile

retryStrategy:
  type: "fixed-quota"
  totalAllowedRetryQuota: 100
  retryPerTestQuota: 3

Kotlin DSL

marathon {
  retryStrategy {
    fixedQuota {
      retryPerTestQuota = 3
      totalAllowedRetryQuota = 100
    }
  }
}

Groovy DSL

marathon {
  retryStrategy {
    fixedQuota {
      retryPerTestQuota = 3
      totalAllowedRetryQuota = 100
    }
  }
}