diff options
| author | Bobby (Babak) Salamat <bsalamat@google.com> | 2017-04-12 13:05:51 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-12 13:05:51 -0700 |
| commit | aa5a6958a22599238b5cffaf67eb472433dbcd6a (patch) | |
| tree | d689e1fee4b5b51c79084cf3527ba2cd7e56c85c | |
| parent | 91f0f615da64ee3e8fa92974324cb73d93dc10b1 (diff) | |
| parent | 3ce9619d02d274866c50d08da1408af8f66ab835 (diff) | |
Merge pull request #526 from bsalamat/e2e_test
Add flaky test debugging info to e2e-tests.md
| -rw-r--r-- | contributors/devel/e2e-tests.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index 1497c800..4df08654 100644 --- a/contributors/devel/e2e-tests.md +++ b/contributors/devel/e2e-tests.md @@ -264,6 +264,18 @@ stale permissions can cause problems. - `sudo iptables -F`, clear ip tables rules left by the kube-proxy. +### Reproducing failures in flaky tests +You can run a test repeatedly until it fails. This is useful when debugging +flaky tests. In order to do so, you need to set the following environment +variable: +```sh +$ export GINKGO_UNTIL_IT_FAILS=true +``` + +After setting the environment variable, you can run the tests as before. The e2e +script adds `--untilItFails=true` to ginkgo args if the environment variable is +set. The flags asks ginkgo to run the test repeatedly until it fails. + ### Federation e2e tests By default, `e2e.go` provisions a single Kubernetes cluster, and any `Feature:Federation` ginkgo tests will be skipped. |