Skip to content

TRT-2068: add renames for tests coming from o/k based on the removal of annotations #282

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

Merged
merged 2 commits into from
May 20, 2025

Conversation

smg247
Copy link
Contributor

@smg247 smg247 commented May 5, 2025

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 5, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 5, 2025

@smg247: This pull request references TRT-2068 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.20.0" version, but no target version was set.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from dgoodwin and xueqzhan May 5, 2025 18:40
@smg247
Copy link
Contributor Author

smg247 commented May 5, 2025

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 5, 2025
@stbenjam
Copy link
Collaborator

stbenjam commented May 8, 2025

It doesn't surprise me mapping.json didn't get updated if we haven't seen the new names in the wild yet.

We need to keep [Suite:openshift/conformance/serial] [Suite:k8s] in the names right now, because origin is still using these. We'll have to implement the Suites via CEL exprs to be able to get rid of these (card in the epic for it).

So we could either add those back in, or wait until we get the suites card done

@smg247
Copy link
Contributor Author

smg247 commented May 8, 2025

It sounds like either way we do it we will have to keep the annotation logic in o/k until after suites are implemented and used in origin. Am I understanding that correctly? If that is the case, it makes more sense to do that first rather than remove parts of the annotation logic, but keep others.

@stbenjam
Copy link
Collaborator

stbenjam commented May 9, 2025

It sounds like either way we do it we will have to keep the annotation logic in o/k until after suites are implemented and used in origin. Am I understanding that correctly?

Not necessarily, you could remove all the annotation code except for this:

https://github.com/openshift/kubernetes/blob/18f7f4cbd6eaf8621dceeb1b0c1738487f547396/openshift-hack/cmd/k8s-tests-ext/k8s-tests.go#L110-L113

And keep the simple logic for serial/parallel determination, and always append [Suite:k8s].

@smg247 smg247 force-pushed the kubernetes-renames branch from 7e8f9cd to c6d58a6 Compare May 12, 2025 20:46
@smg247
Copy link
Contributor Author

smg247 commented May 12, 2025

@stbenjam, I updated the mapping to take into account that the suite info will not be removed from the test names (for now). There are now a few changes when make mapping is run. I think this is due to tests that have at one point been skipped/disabled, but no longer are.

I am going to make a corresponding change to o/k after this to delete all annotation rules that don't pertain to suites, but I first have to wait for openshift/kubernetes#2296 to merge.

This PR can/should merge prior to my forthcoming o/k change anyways.

Edit: openshift/kubernetes#2299 will be ready to merge after this one goes in

@smg247
Copy link
Contributor Author

smg247 commented May 12, 2025

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 12, 2025
@smg247 smg247 force-pushed the kubernetes-renames branch from c6d58a6 to 10d5131 Compare May 12, 2025 20:58
… will not be removed from the name yet

make mapping

update unit test
@smg247 smg247 force-pushed the kubernetes-renames branch from 10d5131 to 35c8ea4 Compare May 15, 2025 13:16
@stbenjam
Copy link
Collaborator

This looks good to me

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 20, 2025
Copy link
Contributor

openshift-ci bot commented May 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smg247, stbenjam

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 20, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit f016a29 into openshift-eng:main May 20, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants