Skip to content

Add flaky-test template to track many flaky-test. #3035

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dlg99 merged 5 commits into from
Feb 14, 2022
Merged

Add flaky-test template to track many flaky-test. #3035

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6294fc4
Fix performance issue to avoid unnessary loop.
mattisonchao Feb 9, 2022
3add1a4
Flaky-test
mattisonchao Feb 10, 2022
bc01f04
Revert "Fix performance issue to avoid unnessary loop."
mattisonchao Feb 10, 2022
d3000a2
Revert useless commit
mattisonchao Feb 10, 2022
b190f86
Fixes label
mattisonchao Feb 10, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions .github/ISSUE_TEMPLATE/flaky_test.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
name: Flaky test
about: Report a flaky test failure
title: 'Flaky-test: test_class.test_method'
labels: ["area/tests", "flaky-tests"]
assignees: ''
---
<!---

Instructions for reporting a flaky test using this issue template:

1. Replace test_class in title and body with the short test class name WITHOUT the package name.
2. Replace test_method in title and body with the test method that failed. Multiple methods are flaky, remove the content that refers to the test method.
3. Replace "relevant parts of the exception stacktrace here" with the a few lines of the stack trace that shows at least the exception message and the line of test code where the stacktrace occurred.
4. Replace "full exception stacktrace here" with the full exception stacktrace from logs. This section will be hidden by default.
5. Remove all unused fields / content to unclutter the reported issue. Remove this comment too.

-->
test_class.test_method is flaky. It fails sporadically.

```
[relevant parts of the exception stacktrace here]
```

<!-- optionally provide the full stacktrace ->
<details>
<summary>Full exception stacktrace</summary>
<code><pre>
full exception stacktrace here
</pre></code>
</details>