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
Add kind/flake issue template #86096
Add kind/flake issue template #86096
Conversation
Update wording to suggest job or test as the target
@spiffxp: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/release-note-none |
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.
Even if folks do continue to use the failing test template for flakes, this should still help categorize more of them with less initial triage needed. 👍
/lgtm
/retest |
/assign @cblecker |
/approve It's a copy/paste of an existing template, meant to help categorize things. I don't think we need a consensus on this one. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cblecker, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
The
kind/failing-test
label should only be used for tests or jobs thatare continuously failing. Today, it's being used for test failures of
any kind, which means flakes are getting under-reported for those who
search the
kind/flake
label.This PR adds a new template that uses the
kind/flake
label to motivatereporting test flakes. I'm updating docs on how to report test flakes and
would like to be able to point to this issue template.
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
/priority important-soon
/sig release
cc @kubernetes/ci-signal
because of CI signal
/sig contributor-experience
because issue templates
/sig testing
because flakes