Skip to content

Conversation

@camilamacedo86
Copy link
Contributor

No description provided.

@openshift-ci-robot
Copy link

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

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 15, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 15, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: camilamacedo86
Once this PR has been reviewed and has the lgtm label, please assign lalatendumohanty 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

@tmshort
Copy link
Contributor

tmshort commented Aug 15, 2025

This does not actually invoke the tests-extension verify from CI.

@camilamacedo86
Copy link
Contributor Author

camilamacedo86 commented Aug 15, 2025

@tmshort
Copy link
Contributor

tmshort commented Aug 15, 2025

OK.
I think it should be part of the regular verify, rather than part of the test builds, however.

#SECTION Development
.PHONY: verify #HELP To verify the code
verify: tidy fmt vet lint
verify: tidy fmt vet lint verify-metadata
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@joelanford commented on PR439, that this should have git diff --exit-code as part of this recipe.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It has @if ! git diff --exit-code >&/dev/null;

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but that should not be buried in verify-manifests

# Do not set globally.
.PHONY: build
build: bindata #HELP Build the extended tests binary
build: #HELP Build the extended tests binary
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might cause a conflict with #438, which we are prioritizing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is fine we can wait that one get merged

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#438 is merged

@tmshort
Copy link
Contributor

tmshort commented Aug 15, 2025

Please rebase this PR onto the latest main and I will take a look

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 15, 2025

@camilamacedo86: 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/okd-scos-e2e-aws-ovn fbae924 link false /test okd-scos-e2e-aws-ovn

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.

@tmshort
Copy link
Contributor

tmshort commented Aug 15, 2025

Why was this closed? My PR #439 was having problems with the verify CI, so I'm giving up on it.
If you rebase it, I will review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants