Skip to content

NO-ISSUE: Run upstream e2e tests tagged with @catalogd-update #605

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
Merged
openshift-merge-bot merged 1 commit into from
Jan 15, 2026
Merged

NO-ISSUE: Run upstream e2e tests tagged with @catalogd-update #605

openshift-merge-bot merged 1 commit into from
Jan 15, 2026
+1 −1

Conversation

@pedjak
Copy link
Contributor

@pedjak pedjak commented Jan 14, 2026 •
edited
Loading

Merge of 9fbe333 enabled proper exposure of docker-registry to upstream e2e tests. Thus, we are now able to run downstream the tests tagged with @catalogd-update

@pedjak
Copy link
Contributor Author

pedjak commented Jan 14, 2026

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 14, 2026
@pedjak
Copy link
Contributor Author

pedjak commented Jan 14, 2026

/test openshift-e2e-aws

3 similar comments
@pedjak
Copy link
Contributor Author

pedjak commented Jan 14, 2026

/test openshift-e2e-aws

@pedjak
Copy link
Contributor Author

pedjak commented Jan 14, 2026

/test openshift-e2e-aws

@droslean
Copy link
Member

droslean commented Jan 14, 2026

/test openshift-e2e-aws

@droslean
Copy link
Member

droslean commented Jan 14, 2026

/retest

@pedjak
UPSTREAM: <carry>: Run upstream e2e tests tagged with @catalogd-update
32e334f 
Merge of openshift@9fbe333
enabled proper exposure of docker-registry to upstream e2e tests. Thus, we are now able to run downstream the tests tagged
with `@catalogd-update`
@pedjak pedjak force-pushed the run-catalogd-update-tests branch from 9c78af5 to 32e334f Compare January 14, 2026 16:44
@pedjak pedjak changed the title UPSTREAM: <carry>: Run upstream @catalogd-update e2e tests NO-ISSUE: Run upstream e2e tests tagged with @catalogd-update Jan 14, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 14, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 14, 2026

@pedjak: This pull request explicitly references no jira issue.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

@pedjak
Copy link
Contributor Author

pedjak commented Jan 14, 2026

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 14, 2026
@perdasilva
Copy link
Contributor

perdasilva commented Jan 14, 2026

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pedjak, perdasilva

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 Jan 14, 2026
@tmshort
Copy link
Contributor

tmshort commented Jan 14, 2026

/test openshift-e2e-aws

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 15, 2026

@pedjak: all tests passed!

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.

@jianzhangbjz
Copy link
Member

jianzhangbjz commented Jan 15, 2026

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 15, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 15, 2026

@jianzhangbjz: The verified label has been added.

Details

In response to this:

/verified bypass

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 52fd8bb into openshift:main Jan 15, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@camilamacedo86 camilamacedo86 Awaiting requested review from camilamacedo86

@oceanc80 oceanc80 Awaiting requested review from oceanc80

1 more reviewer

@perdasilva perdasilva perdasilva approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@perdasilva perdasilva

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@pedjak @droslean @openshift-ci-robot @perdasilva @tmshort @jianzhangbjz