Skip to content

WIP: Full in cluster registry test #486

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
Draft
SamD2021 wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

WIP: Full in cluster registry test #486

SamD2021 wants to merge 3 commits into from

Conversation

@SamD2021
Copy link
Contributor

@SamD2021 SamD2021 commented Jul 23, 2025

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 23, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 23, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 23, 2025

/test all

@openshift-ci
Copy link

openshift-ci bot commented Jul 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SamD2021

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 23, 2025
@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from b79606d to d96568e Compare July 24, 2025 01:17
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 24, 2025

/test all

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from d96568e to b8dfa04 Compare July 24, 2025 02:08
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 24, 2025

/test all

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from b8dfa04 to 99e8c3b Compare July 24, 2025 16:52
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 24, 2025

/test all

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from 99e8c3b to 817a119 Compare July 24, 2025 19:45
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 24, 2025

/test all

1 similar comment
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 24, 2025

/test all

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from 817a119 to ab31490 Compare July 24, 2025 21:53
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 24, 2025

/test all

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from ab31490 to bc37576 Compare July 25, 2025 18:20
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 25, 2025

/test all

1 similar comment
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 25, 2025

/test all

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from bc37576 to 58464d2 Compare July 25, 2025 21:29
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 25, 2025

/test all

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from 58464d2 to a48be2a Compare July 31, 2025 13:36
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 31, 2025

/test all

1 similar comment
@SamD2021
Copy link
Contributor Author

SamD2021 commented Jul 31, 2025

/test all

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 5, 2025
@bn222
Copy link
Contributor

bn222 commented Aug 8, 2025

@SamD2021 can you rebase?

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from a48be2a to c2c4845 Compare August 9, 2025 01:10
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 9, 2025
@SamD2021
Copy link
Contributor Author

SamD2021 commented Aug 9, 2025

/test all

@SamD2021 SamD2021 force-pushed the full-in-cluster-registry-test branch from c2c4845 to f5c301a Compare August 9, 2025 03:52
@SamD2021
Copy link
Contributor Author

SamD2021 commented Aug 9, 2025

/test all

@openshift-ci
Copy link

openshift-ci bot commented Aug 9, 2025

@SamD2021: 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/make-e2e-test-marvell f5c301a link true /test make-e2e-test-marvell
ci/prow/make-e2e-test f5c301a link true /test make-e2e-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.

@openshift-bot
Copy link

openshift-bot commented Nov 8, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 8, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 8, 2025
@openshift-merge-robot
Copy link

openshift-merge-robot commented Nov 8, 2025

PR needs rebase.

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.

@openshift-bot
Copy link

openshift-bot commented Dec 8, 2025

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@SamD2021 @bn222 @openshift-bot @openshift-merge-robot