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-4725: Allow running scenarios with similar name but different type #4570

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

Conversation

ggiguash
Copy link
Contributor

This is particularly useful in dev and QE environments when it is necessary to test both bootc and ostree on the same hypervisor.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 18, 2025

@ggiguash: This pull request references USHIFT-4725 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.19.0" version, but no target version was set.

In response to this:

This is particularly useful in dev and QE environments when it is necessary to test both bootc and ostree on the same hypervisor.

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 Feb 18, 2025
Copy link
Contributor

openshift-ci bot commented Feb 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash

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 Feb 18, 2025
@ggiguash
Copy link
Contributor Author

Subscription flake, retesting
/test e2e-aws-tests-bootc-periodic-arm

@ggiguash ggiguash force-pushed the scenario_run_fix branch 4 times, most recently from 5c69d1b to 0a06d50 Compare February 24, 2025 09:55
@ggiguash
Copy link
Contributor Author

/retest-required

Copy link
Contributor

openshift-ci bot commented Feb 24, 2025

@ggiguash: 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-aws-tests-bootc-arm e7c0acc link true /test e2e-aws-tests-bootc-arm
ci/prow/e2e-aws-tests-bootc-periodic e7c0acc link true /test e2e-aws-tests-bootc-periodic
ci/prow/e2e-aws-tests-bootc e7c0acc link true /test e2e-aws-tests-bootc
ci/prow/e2e-aws-tests-arm e7c0acc link true /test e2e-aws-tests-arm
ci/prow/e2e-aws-tests-periodic e7c0acc link true /test e2e-aws-tests-periodic
ci/prow/e2e-aws-tests e7c0acc link true /test e2e-aws-tests

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. 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.

2 participants