-
Notifications
You must be signed in to change notification settings - Fork 1
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
Release 20.1.3 #1303
Release 20.1.3 #1303
Conversation
/run releases-test-suites |
releases-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a Alternatively, or in addition to, you can also specify |
/test e2e region=default flavour=default |
/test e2e region=default flavour=default |
@paurosello: The following test failed, say
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. I understand the commands that are listed here. |
1 similar comment
@paurosello: The following test failed, say
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. I understand the commands that are listed here. |
* new release * Create announcement.md * Update README.md --------- Co-authored-by: Tobiasz Kukawka <[email protected]>
Checklist
Triggering e2e tests
To trigger the E2E test for each new Release added in this PR add a comment with the following:
/run releases-test-suites
For more details see the README.md