kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #526 from bsalamat/e2e_test 

Add flaky test debugging info to e2e-tests.md
This commit is contained in:
Bobby (Babak) Salamat 2017-04-12 13:05:51 -07:00 committed by GitHub
parent 91f0f615da 3ce9619d02
commit aa5a6958a2
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
contributors/devel/e2e-tests.md
View File

@ -264,6 +264,18 @@ stale permissions can cause problems.
- `sudo iptables -F`, clear ip tables rules left by the kube-proxy. - `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 ### Federation e2e tests
By default, `e2e.go` provisions a single Kubernetes cluster, and any `Feature:Federation` ginkgo tests will be skipped. By default, `e2e.go` provisions a single Kubernetes cluster, and any `Feature:Federation` ginkgo tests will be skipped.