Skip to content

TRT-2260: Create High CPU intervals for nodes #30152

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

xueqzhan
Copy link
Contributor

/hold for testing

@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 21, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 21, 2025

@xueqzhan: This pull request references TRT-2260 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.

In response to this:

/hold for testing

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 added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 21, 2025
@openshift-ci openshift-ci bot requested review from deads2k and sjenning August 21, 2025 19:12
Copy link
Contributor

openshift-ci bot commented Aug 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xueqzhan

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 Aug 21, 2025
Copy link
Contributor

openshift-ci bot commented Aug 22, 2025

@xueqzhan: 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-gcp-ovn-upgrade 025845d link true /test e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-single-node-upgrade 025845d link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-vsphere-ovn 025845d link true /test e2e-vsphere-ovn
ci/prow/e2e-aws-proxy 025845d link false /test e2e-aws-proxy
ci/prow/e2e-aws-disruptive 025845d link false /test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-microshift 025845d link true /test e2e-aws-ovn-microshift
ci/prow/e2e-metal-ipi-ovn-dualstack 025845d link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 025845d link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2 025845d link false /test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-aws-ovn-fips 025845d link true /test e2e-aws-ovn-fips
ci/prow/e2e-gcp-csi 025845d link false /test e2e-gcp-csi
ci/prow/e2e-gcp-ovn-rt-upgrade 025845d link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-gcp-ovn 025845d link true /test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 025845d link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn-techpreview 025845d link false /test e2e-gcp-ovn-techpreview
ci/prow/e2e-metal-ipi-ovn-ipv6 025845d link true /test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

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.

Copy link

openshift-trt bot commented Aug 22, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 025845d

  • "[Jira:"Node / Kubelet"] monitor test high-cpu-metric-collector cleanup" [Total: 38, Pass: 38, Fail: 0, Flake: 0]
  • "[Jira:"Node / Kubelet"] monitor test high-cpu-metric-collector collection" [Total: 38, Pass: 38, Fail: 0, Flake: 0]
  • "[Jira:"Node / Kubelet"] monitor test high-cpu-metric-collector interval construction" [Total: 38, Pass: 38, Fail: 0, Flake: 0]
  • "[Jira:"Node / Kubelet"] monitor test high-cpu-metric-collector preparation" [Total: 38, Pass: 38, Fail: 0, Flake: 0]
  • "[Jira:"Node / Kubelet"] monitor test high-cpu-metric-collector setup" [Total: 38, Pass: 38, Fail: 0, Flake: 0]
  • "[Jira:"Node / Kubelet"] monitor test high-cpu-metric-collector test evaluation" [Total: 38, Pass: 38, Fail: 0, Flake: 0]
  • "[Jira:"Node / Kubelet"] monitor test high-cpu-metric-collector writing to storage" [Total: 38, Pass: 38, Fail: 0, Flake: 0]

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants