-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
legacy-script.sh fixes - junit output and add missing record_command #107740
legacy-script.sh fixes - junit output and add missing record_command #107740
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brianpursley 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 |
/assign soltysh |
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.
Most part seems good for me, just one question.
/cc @oomichi
2ec3a07
to
5a9189b
Compare
ARTIFACTS environment variables if KUBE_JUNIT_REPORT_DIR is not set. Add missing record_command to a couple of tests in legacy-script.sh. Fix some typos in /test/cmd/README.md
5a9189b
to
e120f11
Compare
/retest |
/lgtm |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
/triage accepted |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
I was recently reviewing a PR related to the tests in legacy-script.sh and noticed a few problems in the existing code. This PR fixes those problems.
Added
record_command
to the following tests in legacy-script.sh:Added code to set
KUBE_JUNIT_REPORT_DIR
(copied fromhack/make-rules/test.sh
) to produce junit output in the artifacts directory, so that the individual test results will show up in the build pipeline output's junit section.Fixed some typos in README.md pertaining to how to run individual integration tests.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: