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

fix: patterns in expect script and adjust timeout/exit conditions #635

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nestoracunablanco
Copy link
Contributor

The issue identified was that the string "1" is recognized as a pattern. The latest version of CentOS Stream 9 includes this "pattern" in its boot sequence.

What this PR does / why we need it: s390x enablement

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

NONE

@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Nov 14, 2024
Copy link

openshift-ci bot commented Nov 14, 2024

Hi @nestoracunablanco. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 14, 2024
@0xFelix
Copy link
Member

0xFelix commented Nov 14, 2024

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 14, 2024
@nestoracunablanco
Copy link
Contributor Author

/retest

3 similar comments
@nestoracunablanco
Copy link
Contributor Author

/retest

@nestoracunablanco
Copy link
Contributor Author

/retest

@nestoracunablanco
Copy link
Contributor Author

/retest

@nestoracunablanco
Copy link
Contributor Author

@ksimon1 @jcanocan I've been encountering this error frequently in the CI logs:

 + oc wait --for=condition=Ready --timeout=600s vm/rhel9-highperformance-tiny -n kubevirt
error: timed out waiting for the condition on virtualmachines/rhel9-highperformance-tin

As far as I can tell, this issue is not related to my changes, as they only apply once the VM is ready. Are you experiencing any additional workload with your CI lately?

@nestoracunablanco
Copy link
Contributor Author

@ksimon1 @jcanocan In #636, I increased the timeout, and it worked. Once it's merged, I will rebase and retest the changes.

The issue identified was that the string "1" is recognized as a
pattern. The latest version of CentOS Stream 9 includes this
"pattern" in its boot sequence.

Signed-off-by: Nestor Acuna Blanco <nestor.acuna@ibm.com>
@ksimon1
Copy link
Member

ksimon1 commented Nov 18, 2024

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2024
Copy link
Member

@0xFelix 0xFelix left a comment

Choose a reason for hiding this comment

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

/approve

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0xFelix

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 18, 2024
@nestoracunablanco
Copy link
Contributor Author

/retest

Copy link

openshift-ci bot commented Nov 18, 2024

@nestoracunablanco: 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-common-templates-rhel9 f751b15 link true /test e2e-gcp-common-templates-rhel9
ci/prow/e2e-gcp-common-templates-fedora f751b15 link true /test e2e-gcp-common-templates-fedora
ci/prow/e2e-gcp-common-templates-rhel8 f751b15 link true /test e2e-gcp-common-templates-rhel8
ci/prow/e2e-gcp-common-templates-rhel7 f751b15 link true /test e2e-gcp-common-templates-rhel7

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.

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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants