Skip to content

🤖 Triggering CI on branch 'release-next' after synching to upstream/main#849

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

🤖 Triggering CI on branch 'release-next' after synching to upstream/main#849
serverless-qe wants to merge 1 commit intorelease-nextfrom
release-next-ci

Conversation

@serverless-qe
Copy link
Collaborator

No description provided.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 31f744b and 2 for PR HEAD 1c7498d in total

@openshift-ci
Copy link

openshift-ci bot commented Oct 15, 2025

New changes are detected. LGTM label has been removed.

@serverless-qe serverless-qe force-pushed the release-next-ci branch 2 times, most recently from df086e7 to 7aacf15 Compare February 19, 2026 00:44
@serverless-qe serverless-qe force-pushed the release-next branch 2 times, most recently from 49ed891 to f4aa4f2 Compare February 20, 2026 00:44
@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 2026

@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/4.13-images 55d9c25 link true /test 4.13-images
ci/prow/4.13-e2e-aws-ocp 55d9c25 link true /test 4.13-e2e-aws-ocp

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.

2 participants