diff options
| author | Maria Ntalla <mntalla@pivotal.io> | 2019-02-08 13:12:25 +0000 |
|---|---|---|
| committer | Maria Ntalla <mntalla@pivotal.io> | 2019-02-08 13:12:25 +0000 |
| commit | 2b06c05299a13af618c1c69fa0a6a0ba5233acb6 (patch) | |
| tree | 9ec71b457dc40e8939e62b758f79d997f4f29192 /contributors | |
| parent | 62b6520c421855ec19995fd6ed247fe103c8d590 (diff) | |
Escalation->Escalating
Opt for active voicing for better readability.
Diffstat (limited to 'contributors')
| -rw-r--r-- | contributors/devel/testing.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/devel/testing.md b/contributors/devel/testing.md index 18a7b1b7..7053e536 100644 --- a/contributors/devel/testing.md +++ b/contributors/devel/testing.md @@ -235,9 +235,9 @@ Click on `Details` and look at the [`gubernator`](gubernator.k8s.io/) output for #### 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) + - If no, open a new issue and notify the appropriate SIG (see: Escalating failures to a SIG) -#### SIG test escalation +#### Escalating failures to a SIG - 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 |
