summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-09-20 10:16:44 -0700
committerGitHub <noreply@github.com>2018-09-20 10:16:44 -0700
commitec12a2f30c8d33fa16fe34f737502c471146ed7f (patch)
treea8433611bb2726d3de48b3ed7ba865aa059378c7
parentc49177aacd88784a031bd2c1eb57b18752be3cc2 (diff)
parent3a13fb1487badd1c746978024fec964442d6e3b3 (diff)
Merge pull request #2693 from tpepper/master
devel guide: note where to track flaky tests
-rw-r--r--contributors/devel/flaky-tests.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/contributors/devel/flaky-tests.md b/contributors/devel/flaky-tests.md
index f06bb078..14f8da9e 100644
--- a/contributors/devel/flaky-tests.md
+++ b/contributors/devel/flaky-tests.md
@@ -15,6 +15,19 @@ what caused the failure.
Note that flakes can occur in unit tests, integration tests, or end-to-end
tests, but probably occur most commonly in end-to-end tests.
+## Hunting Flakes
+
+You may notice lots of your PRs or ones you watch are having a common
+pre-submit failure, but less frequent issues that are still of concern take
+more analysis over time. There are metrics recorded and viewable in:
+- [TestGrid](https://k8s-testgrid.appspot.com/presubmits-kubernetes-blocking#Summary)
+- [Velodrome](http://velodrome.k8s.io/dashboard/db/bigquery-metrics?orgId=1)
+
+It is worth noting tests are going to fail in presubmit a lot due
+to unbuildable code, but that wont happen as much on the same commit unless
+there's a true issue in the code or a broader problem like a dep failed to
+pull in.
+
## Filing issues for flaky tests
Because flakes may be rare, it's very important that all relevant logs be