-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
deleting redundant test file #3556
Conversation
dagv1beta1_test.go was created during the transition from alpha to beta API. Now that, the transition is over and we have identical tests in both tests file, its safe to delete one of them. Other changes include, rearranging local functions in the end of the file, and moving _invalid to the end of valid tests.
/test pull-tekton-pipeline-integration-tests |
/lgtm nice! |
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.
/meow
In response to this:
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: vdemeester 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 |
Changes
Pure refactoring - no test content changed in
dag_test.go
except using*v1beta1.NewArrayOrString
instead ofv1beta1.ArrayOrString{
intestGraph
.dagv1beta1_test.go
was created during the transition from alpha to beta API. Now that, the transition is over and we have identical tests in both tests file, it's safe to delete one of them.Other changes include, rearranging local functions in the end of the file, and moving _invalid to the end of valid tests.
/kind cleanup
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes