Skip to content

🤖 Triggering CI on branch 'release-next' after syncing to upstream/main #1436

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 syncing to upstream/main #1436

wants to merge 1 commit into from

Conversation

serverless-qe
Copy link
Collaborator

No description provided.

@openshift-ci openshift-ci bot requested review from alanfx and dsimansk April 30, 2025 00:59
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Apr 30, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: serverless-qe
Once this PR has been reviewed and has the lgtm label, please assign mvinkler for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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
Copy link

openshift-ci bot commented Jun 1, 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 7297111 link true /test 417-images
ci/prow/417-test-e2e 7297111 link true /test 417-test-e2e
ci/prow/418-test-e2e cb4dc5c link true /test 418-test-e2e
ci/prow/418-images cb4dc5c link true /test 418-images

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

@alanfx alanfx Awaiting requested review from alanfx

@dsimansk dsimansk Awaiting requested review from dsimansk

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

Successfully merging this pull request may close these issues.
1 participant
@serverless-qe