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
hack/verify-e2e-suites.sh: non-zero exit code when there were errors #124351
Conversation
The script correctly reported errors, but did not return a non-zero exit code. Therefore errors would have been overlooked during pull-kubernetes-verify runs.
Please note that we're already in Test Freeze for the Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Apr 17 13:56:00 UTC 2024. |
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/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly 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 |
/lgtm |
LGTM label has been added. Git tree hash: 71f7eb1b593c089ac2264ec7f0c1642d31d42490
|
/sig testing |
What type of PR is this?
/kind bug
/kind failing-test
What this PR does / why we need it:
The script correctly reported errors, but did not return a non-zero exit code. Therefore errors would have been overlooked during pull-kubernetes-verify runs.
Does this PR introduce a user-facing change?