Skip to content

USHIFT-6349: Reduce VMs in CI #5820

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.

Sign up for GitHub

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

Jump to bottom
Draft
pacevedom wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

USHIFT-6349: Reduce VMs in CI #5820

pacevedom wants to merge 1 commit into from
+5 −33

Conversation

@pacevedom
Copy link
Contributor

@pacevedom pacevedom commented Nov 27, 2025

No description provided.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 27, 2025 •
edited by openshift-ci bot
Loading

@pacevedom: This pull request references USHIFT-6349 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 task to target the "4.21.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 Nov 27, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 27, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 27, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@pacevedom
Copy link
Contributor Author

pacevedom commented Nov 27, 2025

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 27, 2025

@pacevedom: The following commands are available to trigger required jobs:

/test e2e-aws-ai-model-serving

/test e2e-aws-footprint-and-performance

/test e2e-aws-tests

/test e2e-aws-tests-arm

/test e2e-aws-tests-bootc

/test e2e-aws-tests-bootc-arm

/test e2e-aws-tests-bootc-periodic

/test e2e-aws-tests-bootc-periodic-arm

/test e2e-aws-tests-bootc-release

/test e2e-aws-tests-bootc-release-arm

/test e2e-aws-tests-bootc-upstream

/test e2e-aws-tests-bootc-upstream-arm

/test e2e-aws-tests-cache

/test e2e-aws-tests-cache-arm

/test e2e-aws-tests-periodic

/test e2e-aws-tests-periodic-arm

/test e2e-aws-tests-release

/test e2e-aws-tests-release-arm

/test ocp-full-conformance-rhel-eus

/test ocp-full-conformance-serial-rhel-eus

/test test-rpm

/test test-unit

/test verify

The following commands are available to trigger optional jobs:

/test images

/test security

/test test-rebase

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-microshift-main-e2e-aws-tests

pull-ci-openshift-microshift-main-e2e-aws-tests-arm

pull-ci-openshift-microshift-main-e2e-aws-tests-bootc

pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm

pull-ci-openshift-microshift-main-images

pull-ci-openshift-microshift-main-security

pull-ci-openshift-microshift-main-test-unit

pull-ci-openshift-microshift-main-verify

In response to this:

/test ?

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
Copy link
Contributor

openshift-ci bot commented Nov 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacevedom

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 Nov 27, 2025
@pacevedom
Copy link
Contributor Author

pacevedom commented Nov 27, 2025

/test e2e-aws-tests

ggiguash
ggiguash reviewed Nov 27, 2025
View reviewed changes
test/scenarios/presubmits/[email protected] Outdated
Copy link
Contributor

@ggiguash ggiguash Nov 27, 2025

Choose a reason for hiding this comment

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

Nit: we currently use @standard-suite1.sh suffix, so can we use the same naming here?
Something like: @standard-config1?

ggiguash
ggiguash reviewed Nov 27, 2025
View reviewed changes
test/scenarios/presubmits/[email protected] Outdated
suites/logscan \
suites/storage/ \
suites/upgrades/upgrade-fails.robot \
suites/upgrades/upgrade-fails-then-recovers.robot
Copy link
Contributor

@ggiguash ggiguash Nov 27, 2025

Choose a reason for hiding this comment

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

Let's watch the timing these tests take. We should try not to prolong the job runtime with this change.

ggiguash
ggiguash reviewed Nov 27, 2025
View reviewed changes
test/scenarios/presubmits/[email protected] Outdated
# is in a good state at the start of each test. We could have
# separated them and run them as separate scenarios, but did not
#want to spend the resources on a new VM.
export TEST_RANDOMIZATION=none
Copy link
Contributor

@ggiguash ggiguash Nov 27, 2025

Choose a reason for hiding this comment

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

Note that this only applies to logscan, but we're removing randomization from all the other tests too. Can we call run_tests twice? Once with and once without randomization?

@pacevedom
Copy link
Contributor Author

pacevedom commented Nov 28, 2025

/test e2e-aws-tests

@pacevedom
Copy link
Contributor Author

pacevedom commented Nov 28, 2025

/test e2e-aws-tests

@pacevedom
Copy link
Contributor Author

pacevedom commented Nov 28, 2025

/test e2e-aws-tests
/test e2e-aws-tests-bootc

@pacevedom
Copy link
Contributor Author

pacevedom commented Nov 28, 2025

/test e2e-aws-tests

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 28, 2025

@pacevedom: The following test 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-aws-tests-bootc 1766411 link true /test e2e-aws-tests-bootc

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

Reviewers

1 more reviewer

@ggiguash ggiguash ggiguash left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@pacevedom @openshift-ci-robot @ggiguash