From 3ce9619d02d274866c50d08da1408af8f66ab835 Mon Sep 17 00:00:00 2001 From: Bobby Salamat Date: Tue, 11 Apr 2017 11:35:39 -0700 Subject: Add flaky test debugging info to e2e-tests.md --- contributors/devel/e2e-tests.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) 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. -- cgit v1.2.3