Skip to content

🤖 triggering CI on branch 'release-next' after synching from upstream/main #1270

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
Open
wants to merge 1 commit into
base: release-next
Choose a base branch
from
Open

🤖 triggering CI on branch 'release-next' after synching from upstream/main #1270

wants to merge 1 commit into from

Conversation

serverless-qe
Copy link

No description provided.

@openshift-ci openshift-ci bot requested review from dsimansk and jrangelramos April 25, 2025 01:05
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Apr 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: serverless-qe

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

1 similar comment
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Apr 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: serverless-qe

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

/retest-required

Remaining retests: 0 against base HEAD d7dec54 and 2 for PR HEAD 591fc8e in total

@gauron99
Copy link

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD d7dec54 and 2 for PR HEAD 591fc8e in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD d7dec54 and 2 for PR HEAD 591fc8e in total

@openshift-ci openshift-ci bot removed the lgtm label Apr 26, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Apr 26, 2025

New changes are detected. LGTM label has been removed.

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jun 7, 2025

@serverless-qe: 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/417-images 3b537f9 link true /test 417-images
ci/prow/417-unit 3b537f9 link true /test 417-unit
ci/prow/417-e2e-oncluster-test 3b537f9 link true /test 417-e2e-oncluster-test
ci/prow/418-images a9f2764 link true /test 418-images
ci/prow/418-unit a9f2764 link true /test 418-unit
ci/prow/418-e2e-oncluster-test a9f2764 link true /test 418-e2e-oncluster-test

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

@dsimansk dsimansk Awaiting requested review from dsimansk

@jrangelramos jrangelramos Awaiting requested review from jrangelramos

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
approved kind/sync-fork-to-upstream
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@serverless-qe @openshift-ci-robot @gauron99