Skip to content

[release-4.22] OCPBUGS-98400: E2E: Add functional test cases checking GOMAXPROCS#1561

Open
openshift-cherrypick-robot wants to merge 3 commits into
openshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-1556-to-release-4.22
Open

[release-4.22] OCPBUGS-98400: E2E: Add functional test cases checking GOMAXPROCS#1561
openshift-cherrypick-robot wants to merge 3 commits into
openshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-1556-to-release-4.22

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #1556

/assign mrniranjan

Following tests were added:
1. Verify GOMAXPROCS configuration is injected when Performance Profile
   is applied
2. Create a go-based container with below scenarios
   BestEffort - No Requests/Limits
   Burstable low - cpu:100m requests, no limits
   Burstable high - cpu:8 requests, no limits (2x overcommit)
   Guaranteed - cpu:1 request + limit
   Guaranteed with runtime class - cpu:1 request + limit
   Init + app container - cpu:100m on both, no limits
   Burstable with limit - cpu:2 request, cpu:4 limit

Signed-off-by: Niranjan M.R <mniranja@redhat.com>
Signed-off-by: Niranjan M.R <mniranja@redhat.com>
Signed-off-by: Niranjan M.R <mniranja@redhat.com>
@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0d81e5c1-13a6-476b-b2b6-7b7a283219c9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci openshift-ci Bot requested review from ffromani and swatisehgal July 10, 2026 13:21
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-98399 has been cloned as Jira Issue OCPBUGS-98400. Will retitle bug to link to clone.
/retitle [release-4.22] OCPBUGS-98400: E2E: Add functional test cases checking GOMAXPROCS

Details

In response to this:

This is an automated cherry-pick of #1556

/assign mrniranjan

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 commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign yanirq for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 changed the title [release-4.22] OCPBUGS-98399: E2E: Add functional test cases checking GOMAXPROCS [release-4.22] OCPBUGS-98400: E2E: Add functional test cases checking GOMAXPROCS Jul 10, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jul 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-98400, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-98399 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-98399 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
  • bug has dependents

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #1556

/assign mrniranjan

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 commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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-pao 87341d0 link true /test e2e-gcp-pao
ci/prow/e2e-aws-operator 87341d0 link true /test e2e-aws-operator
ci/prow/lint 87341d0 link true /test lint
ci/prow/e2e-hypershift-pao 87341d0 link true /test e2e-hypershift-pao
ci/prow/vet 87341d0 link true /test vet

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

jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.

3 participants