-
Notifications
You must be signed in to change notification settings - Fork 41.7k
Expand Test Grid related info for failing and flaking tests #135194
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
base: master
Are you sure you want to change the base?
Expand Test Grid related info for failing and flaking tests #135194
Conversation
|
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-sigs/prow repository. |
|
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: benjaminapetersen The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/sig testing release |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Improves the
FailingandFlakingtest templates by providing explicit guidance to provideTest GridNameandURLto the issue. Folks serving on release team roles have to monitor the state of Test Grid manually. Having very clear correlation between GitHub issues and Test Grid will reduce some of the busywork overhead as well as help ensure we avoid duplicate issues for the same test problems.Which issue(s) this PR is related to:
N/A