Skip to content
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

OCPBUGS-18650: Memory manager E2E test fixes #784

Merged

Conversation

mrniranjan
Copy link
Contributor

Minor left over fixes of Memory manager E2E Test cases

Minor left over fixes of Memory manager E2E Test cases

Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>
@mrniranjan
Copy link
Contributor Author

/test e2e-gcp-pao-updating-profile

@mrniranjan mrniranjan changed the title Memory manager E2E test fixes OCPBUGS-18650: Memory manager E2E test fixes Sep 7, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Sep 7, 2023
@openshift-ci-robot
Copy link
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (mniranja@redhat.com), skipping review request.

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

In response to this:

Minor left over fixes of Memory manager E2E Test cases

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Sep 7, 2023
Copy link
Contributor

@ffromani ffromani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm
/hold

LGTM bar a question inside

profile.Spec.WorkloadHints = &performancev2.WorkloadHints{
RealTime: pointer.Bool(true),
}
profile.Spec.WorkloadHints = &performancev2.WorkloadHints{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so we are always forcing the hints to this value. Is that what we really need to do? Is it a problem if we overwrite other hints?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right because if we set RealTime to true, then having a profile with Realtime performance hint being disabled would cause issues, So we wanted to make it default to have Realtime workload hint to be true, other workload hints are not an issue.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provided we restore the profile correctly if needed, and we don't pollute any global state (e.g. is the profile instance being changed unique to the testcase or shared among testcases?), fine for me.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we take backup and restore after the tests.

profile.Spec.WorkloadHints = &performancev2.WorkloadHints{
RealTime: pointer.Bool(true),
}
profile.Spec.WorkloadHints = &performancev2.WorkloadHints{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above

@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 Sep 12, 2023
@ffromani
Copy link
Contributor

/hold cancel

questions answered

@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 Sep 12, 2023
@ffromani
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 12, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 12, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, mrniranjan

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 Sep 12, 2023
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0707c79 and 2 for PR HEAD d526bbd in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD e27dac7 and 1 for PR HEAD d526bbd in total

@mrniranjan
Copy link
Contributor Author

/retest-required

@mrniranjan
Copy link
Contributor Author

/test e2e-gcp-pao

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

@mrniranjan: all tests passed!

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

@openshift-merge-robot openshift-merge-robot merged commit 6288725 into openshift:master Sep 19, 2023
13 checks passed
@openshift-ci-robot
Copy link
Contributor

@mrniranjan: Jira Issue OCPBUGS-18650: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-18650 has been moved to the MODIFIED state.

In response to this:

Minor left over fixes of Memory manager E2E Test cases

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/test-infra repository.

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/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants