-
Notifications
You must be signed in to change notification settings - Fork 4.8k
remove legacy recovery tests #27917
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
remove legacy recovery tests #27917
Conversation
|
/lgtm |
| "[sig-arch][Feature:ClusterUpgrade] Cluster should be upgradeable after finishing upgrade [Late][Suite:upgrade]": "", | ||
|
|
||
| "[sig-arch][Feature:ClusterUpgrade] Cluster should be upgradeable before beginning upgrade [Early][Suite:upgrade]": "", |
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.
This is not related to our cleanup right? And the test still seems to be there:
origin/test/e2e/upgrade/upgrade.go
Lines 142 to 146 in 2d41e52
| var _ = g.Describe("[sig-arch][Feature:ClusterUpgrade]", func() { | |
| f := framework.NewDefaultFramework("cluster-upgrade") | |
| f.SkipNamespaceCreation = true | |
| g.It("Cluster should be upgradeable before beginning upgrade [Early][Suite:upgrade]", func() { |
We might want to double check if we aren't disabling this unintentionally.
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.
good point, no idea how that got into it...
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.
okay that's a really weird issue, it's a completely different folder. On the master branch I don't have that change generated.
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.
okay that's a really weird issue, it's a completely different folder. On the master branch I don't have that change generated.
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.
there was an implicit dependency on the e2e module, I've added it manually again now
b4d1d4e to
d25b76b
Compare
|
/approve |
4bfba18 to
cb558e7
Compare
|
@bparees could you please take a look when you have some time? We have successfully replaced the existing tests with two new presubmits: which are running now, which means we can clean this old bastion-ssh based tests up :) |
|
/approve |
|
/lgtm |
|
/retest-required |
|
/hold |
|
/hold cancel |
cb558e7 to
57f7006
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, dusk125, hasbro17, tjungblu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@tjungblu: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
cleaning up the old tests and the bastion ssh code