-
Notifications
You must be signed in to change notification settings - Fork 962
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.
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
Conversation
|
@merlimat @eolivelli @dlg99 @nicoloboschi PTAL :) |
.github/ISSUE_TEMPLATE/flaky_test.md
Outdated
| name: Flaky test | ||
| about: Report a flaky test failure | ||
| title: 'Flaky-test: test_class.test_method' | ||
| labels: ["component/test", "flaky-tests"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
component/test doesn't exist. Please use area/tests. We can create the flaky-tests label @dlg99 @eolivelli
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nicoloboschi PTAL : )
|
rerun failure checks |
### Motivation I found many flaky-test like apache#3031 apache#3034 apache#3033. Because many flaky tests are actually production code issues so I think it's a good way to add flaky-test template to track them ### Changes - Add flaky-test template. Reviewers: Andrey Yegorov <None> This closes apache#3035 from mattisonchao/template_flaky_test
### Motivation I found many flaky-test like apache#3031 apache#3034 apache#3033. Because many flaky tests are actually production code issues so I think it's a good way to add flaky-test template to track them ### Changes - Add flaky-test template. Reviewers: Andrey Yegorov <None> This closes apache#3035 from mattisonchao/template_flaky_test
Motivation
I found many flaky-test like #3031 #3034 #3033.
Because many flaky tests are actually production code issues so I think it's a good way to add flaky-test template to track them
Changes