diff options
| author | Maria Ntalla <mntalla@pivotal.io> | 2019-01-23 16:15:25 +0000 |
|---|---|---|
| committer | Maria Ntalla <mntalla@pivotal.io> | 2019-01-23 16:15:25 +0000 |
| commit | 56b9e2a4c079d4a13ee7c56789100a4e430b9567 (patch) | |
| tree | b242deae73eb921d6f28aad0cb4ab432d2b13b35 | |
| parent | a7642fc5d85d6d35b2ebeb6d1129999c37595e76 (diff) | |
Draft content related to debugging CI
Not complete yet, just outline.
| -rw-r--r-- | contributors/devel/testing.md | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/contributors/devel/testing.md b/contributors/devel/testing.md index 60f83b53..6b119e81 100644 --- a/contributors/devel/testing.md +++ b/contributors/devel/testing.md @@ -225,3 +225,38 @@ version and the watch cache test is skipped. ## End-to-End tests Please refer to [End-to-End Testing in Kubernetes](e2e-tests.md). + +## Running your contribution in the Kubernetes CI +Once you open a PR, prow will run pre-submit tests in CI. + +### Troubleshooting a failure +Click on `Details` and look at the [`gubernator`](gubernator.k8s.io/) output for the test. + +#### Troubleshooting failures/flakes that are not caused by your change +- Check if an issue has already been opened for that test failure/flake + - If yes, comment on it and link your PR, the failed run that affected you and any other information you think might be relevant + - If no, open a new issue and notify the appropriate SIG (see: SIG test escalation) + +#### SIG test escalation +- Figure out corresponding sig from test name/description +- Mention the sig's github handle on the issue, optionally cc the SIG's chair(s) (locate them under kubernetes/community/sig-<name>) +- Optionally (or if you haven't heard back on the issue after 24h) reach out to the SIG on slack + +### Testgrid +You can see CI in testgrid, either: +- Starting from gubernator report, or +- testgrid.k8s.io + +testgrid is organised in: +- tests + - collection of assertions in a test file + - each test is typically owned by a single SIG + - each test is represented as a row on the grid +- jobs + - collection of tests + - each job is typically owned by a single SIG + - each job is represented as a tab +- dashboards + - collection of jobs + - each dashboard is represented as a button + - some dashboards collect jobs/tests in the domain of a specific SIG (named after and owned by those sigs), and dashboards to monitor project wide health (owned by sig-release) |