Skip to content

OPRUN-4055: [OLMv1] Remove olmv1.go tests since those has been executed by OTE#30072

Merged
sdodson merged 1 commit intoopenshift:mainfrom
camilamacedo86:remove-olmv1
Aug 13, 2025
Merged

OPRUN-4055: [OLMv1] Remove olmv1.go tests since those has been executed by OTE#30072
sdodson merged 1 commit intoopenshift:mainfrom
camilamacedo86:remove-olmv1

Conversation

@camilamacedo86
Copy link
Copy Markdown
Contributor

@camilamacedo86 camilamacedo86 commented Aug 6, 2025

@camilamacedo86 camilamacedo86 changed the title [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo Aug 6, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 6, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 6, 2025

@camilamacedo86: This pull request references OPRUN-4055 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 story to target the "4.20.0" version, but no target version was set.

Details

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-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 6, 2025

@camilamacedo86: This pull request references OPRUN-4055 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 story to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Blocked by: openshift/operator-framework-operator-controller#418

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 ankitathomas and hasbro17 August 6, 2025 18:43
@camilamacedo86 camilamacedo86 changed the title OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo (Blocked by: openshift/operator-framework-operator-controller#418 )OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo Aug 7, 2025
@openshift-trt
Copy link
Copy Markdown

openshift-trt Bot commented Aug 7, 2025

Job Failure Risk Analysis for sha: ae30c4a

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-disruptive IncompleteTests
Tests for this run (31) are below the historical average (207): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@camilamacedo86 camilamacedo86 changed the title (Blocked by: openshift/operator-framework-operator-controller#418 )OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo (Blocked by: openshift/operator-framework-operator-controller#418 AND OTHERS )OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo Aug 8, 2025
@camilamacedo86 camilamacedo86 changed the title (Blocked by: openshift/operator-framework-operator-controller#418 AND OTHERS )OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo (DO NOT MERGE) - (Blocked by: openshift/operator-framework-operator-controller#418)OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo Aug 8, 2025
@camilamacedo86 camilamacedo86 changed the title (DO NOT MERGE) - (Blocked by: openshift/operator-framework-operator-controller#418)OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo (DO NOT MERGE) - OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo Aug 8, 2025
@camilamacedo86
Copy link
Copy Markdown
Contributor Author

/hold

Until: openshift/operator-framework-operator-controller#423 get merged
AND
we have the signal that we can remove

@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 Aug 8, 2025
@camilamacedo86 camilamacedo86 changed the title (DO NOT MERGE) - OPRUN-4055: [OLMv1] Migrate olmv1.go tests to OTE and operator-controller repo (DO NOT MERGE) - OPRUN-4055: [OLMv1] Remove olmv1.go tests since those has been executed by origin Aug 11, 2025
@openshift-trt
Copy link
Copy Markdown

openshift-trt Bot commented Aug 11, 2025

Job Failure Risk Analysis for sha: f70143a

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-hypershift-conformance Medium
[sig-sippy] infrastructure should work
This test has passed 85.71% of 14 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:hypershift JobTier:standard Network:ovn NetworkStack:ipv4 Owner:eng Platform:aws Procedure:none SecurityMode:default Topology:external Upgrade:micro] in the last week.

@camilamacedo86 camilamacedo86 changed the title (DO NOT MERGE) - OPRUN-4055: [OLMv1] Remove olmv1.go tests since those has been executed by origin OPRUN-4055: [OLMv1] Remove olmv1.go tests since those has been executed by origin Aug 12, 2025
@camilamacedo86
Copy link
Copy Markdown
Contributor Author

/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 Aug 12, 2025
@tmshort
Copy link
Copy Markdown
Contributor

tmshort commented Aug 12, 2025

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 12, 2025
@camilamacedo86 camilamacedo86 changed the title OPRUN-4055: [OLMv1] Remove olmv1.go tests since those has been executed by origin OPRUN-4055: [OLMv1] Remove olmv1.go tests since those has been executed by OTE Aug 12, 2025
@xueqzhan
Copy link
Copy Markdown
Contributor

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, tmshort, xueqzhan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Aug 12, 2025
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 8854246 and 2 for PR HEAD 4b0fe03 in total

@camilamacedo86
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-upgrade

@openshift-trt
Copy link
Copy Markdown

openshift-trt Bot commented Aug 13, 2025

Job Failure Risk Analysis for sha: 4b0fe03

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-techpreview-serial-1of2 IncompleteTests
Tests for this run (105) are below the historical average (1536): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 13, 2025

@camilamacedo86: This pull request references OPRUN-4055 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 story to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Blocked by: openshift/operator-framework-operator-controller#418

Closes: #30063

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-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 4ad9050 and 1 for PR HEAD 4b0fe03 in total

@sdodson sdodson merged commit 1b893d5 into openshift:main Aug 13, 2025
29 of 47 checks passed
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 13, 2025

@camilamacedo86: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-single-node 4b0fe03 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 4b0fe03 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-ovn-dualstack 4b0fe03 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-ovn-single-node-serial 4b0fe03 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-ovn-techpreview-serial-1of2 4b0fe03 link false /test e2e-gcp-ovn-techpreview-serial-1of2
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 4b0fe03 link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-azure 4b0fe03 link false /test e2e-azure
ci/prow/e2e-agnostic-ovn-cmd 4b0fe03 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2 4b0fe03 link false /test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-aws-ovn-cgroupsv2 4b0fe03 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn 4b0fe03 link false /test e2e-aws-ovn
ci/prow/e2e-aws-proxy 4b0fe03 link false /test e2e-aws-proxy
ci/prow/e2e-aws-ovn-single-node-upgrade 4b0fe03 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/okd-scos-e2e-aws-ovn 4b0fe03 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-disruptive 4b0fe03 link false /test e2e-aws-disruptive
ci/prow/e2e-gcp-ovn-rt-upgrade 4b0fe03 link false /test e2e-gcp-ovn-rt-upgrade

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

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.

5 participants