diff options
| author | Daniel Smith <dbsmith@google.com> | 2016-01-29 11:47:33 -0800 |
|---|---|---|
| committer | Daniel Smith <dbsmith@google.com> | 2016-01-29 11:47:33 -0800 |
| commit | 4ba595e7f6ae4394f5d1bd4ae3be0f86c5881191 (patch) | |
| tree | ba7114703e7019fa9f3245b3909d8c05d6b5de64 | |
| parent | 7816368e07cbb396873223947ae5b9d7d26c96ff (diff) | |
add instructions to ease follow-up
| -rw-r--r-- | flaky-tests.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/flaky-tests.md b/flaky-tests.md index 4047a7f9..ce838915 100644 --- a/flaky-tests.md +++ b/flaky-tests.md @@ -58,7 +58,10 @@ discoverable from the issue. flake is exactly the same, add a comment instead of making a new issue. 2. If you make a new issue, you should title it with the test name, prefixed by "e2e/unit/integration flake:" (whichever is appropriate) -3. Reference any old issues you found in step one. +3. Reference any old issues you found in step one. Also, make a comment in the + old issue referencing your new issue, because people monitoring only their + email do not see the backlinks github adds. Alternatively, tag the person or + people who most recently worked on it. 4. Paste, in block quotes, the entire log of the individual failing test, not just the failure line. 5. Link to durable storage with the rest of the logs. This means (for all the |