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

USHIFT-2990: Early warning low latency job #3721

Merged
merged 1 commit into from
Aug 7, 2024

Conversation

pmtk
Copy link
Member

@pmtk pmtk commented Aug 5, 2024

No description provided.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 5, 2024

@pmtk: This pull request references USHIFT-2990 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.17.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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 5, 2024
@pmtk
Copy link
Member Author

pmtk commented Aug 5, 2024

Used by openshift/release#55035

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 5, 2024
@pmtk
Copy link
Member Author

pmtk commented Aug 5, 2024

/retest

@pacevedom
Copy link
Contributor

/retest-required

@pmtk pmtk force-pushed the low-latency/warning-job branch 4 times, most recently from 677e00d to 347eeac Compare August 6, 2024 08:47

set -xeuo pipefail

retries=15
Copy link
Contributor

Choose a reason for hiding this comment

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

Any reason for 7.5m wait? Let's make it 10m at least?

Copy link
Member Author

Choose a reason for hiding this comment

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

Idk, I just copied it from somewhere else :) Changed

TEST_DURATION=$(( 2 * 60 ))
POD=hwlatdetect

sudo tee /tmp/hwlatdetect.yaml << EOF
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we add a description on what we're running in the pod?

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, should we use mktemp for the file in /tmp?

Copy link
Member Author

Choose a reason for hiding this comment

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

Added desc, but didn't use mktemp - it's annoying for manually iterating on the yaml


sudo subscription-manager repos --enable rhel-9-for-x86_64-rt-rpms
sudo dnf install kernel-rt realtime-setup realtime-tests -y
sudo grubby --set-default="$(ls /boot/vmlinuz*rt)"
Copy link
Contributor

Choose a reason for hiding this comment

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

Kernel files tend to accumulate. I understand that we're installing kernel-rt at this spot, but can we still make the code more robust?
Basically, we should

  • rpm -q kernel-rt | sort | tail -1
  • Use the value in grubby command

# shellcheck source=scripts/ci-footprint-and-performance/tests/functions.sh
source "${SCRIPTDIR}/functions.sh"

TEST_DURATION=$(( 2 * 60 ))
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't 2m too short? I would run at least 5m each, possibly even more time.

Copy link
Member Author

Choose a reason for hiding this comment

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

Don't think so, default value is 10s and in RHEL docs I've seen 60 seconds. This is just sanity for additional results if we see something weird in oslat. Oslat is the key test here.

@pmtk
Copy link
Member Author

pmtk commented Aug 6, 2024

/hold

Need to retest with CI job

@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 6, 2024
@pmtk
Copy link
Member Author

pmtk commented Aug 7, 2024

/unhold

@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 7, 2024
@pmtk pmtk force-pushed the low-latency/warning-job branch 3 times, most recently from bf7d6f5 to 5d712aa Compare August 7, 2024 10:08
@pmtk
Copy link
Member Author

pmtk commented Aug 7, 2024

/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 Aug 7, 2024
@pmtk
Copy link
Member Author

pmtk commented Aug 7, 2024

/unhold

@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 7, 2024
@ggiguash
Copy link
Contributor

ggiguash commented Aug 7, 2024

/lgtm

Copy link
Contributor

openshift-ci bot commented Aug 7, 2024

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

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 7, 2024
Copy link
Contributor

openshift-ci bot commented Aug 7, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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-merge-bot openshift-merge-bot bot merged commit 06f89a2 into openshift:main Aug 7, 2024
8 checks passed
@pmtk pmtk deleted the low-latency/warning-job branch August 7, 2024 12:41
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.

4 participants