Skip to content

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

Open
serverless-qe wants to merge 1 commit into
release-nextfrom
release-next-ci
Open

🤖 triggering CI on branch 'release-next' after synching from upstream/main#1505
serverless-qe wants to merge 1 commit into
release-nextfrom
release-next-ci

Conversation

@serverless-qe
Copy link
Copy Markdown

No description provided.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 25, 2026

[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

Details 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
Copy link
Copy Markdown

openshift-ci Bot commented Apr 26, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 15, 2026

@serverless-qe: 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/420-e2e-oncluster-test 17d18e1 link true /test 420-e2e-oncluster-test

Full PR test history. Your PR dashboard.

Details

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant