Skip to content
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.

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

NO-JIRA: makefile: ensure bindata #1116

Merged
merged 1 commit into from
Jul 22, 2024

Conversation

ffromani
Copy link
Contributor

0_config requires now pkg/manifests, so we need
to make sure bindata is generated

extracted from #1019 because it helps other PRs too: #1019 (comment) (xref: #1089)

0_config requires now `pkg/manifests`, so we need
to make sure bindata is generated

Signed-off-by: Francesco Romani <[email protected]>
@openshift-ci openshift-ci bot requested review from jmencak and MarSik July 22, 2024 06:22
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2024
@ffromani
Copy link
Contributor Author

/label acknowledge-critical-fixes-only

if CI passes, this change can't break the product

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Jul 22, 2024
@Tal-or
Copy link
Contributor

Tal-or commented Jul 22, 2024

/lgtm
Thanks

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2024
@jmencak
Copy link
Contributor

jmencak commented Jul 22, 2024

/approve

Copy link
Contributor

openshift-ci bot commented Jul 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, jmencak

The full list of commands accepted by this bot can be found here.

The pull request process is described 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

@ffromani
Copy link
Contributor Author

level=error msg=Attempted to gather ClusterOperator status after installation failure: listing ClusterOperator objects: Get "https://api.ci-op-1dnz5m6r-13bd6.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp 34.171.110.204:6443: connect: connection refused

@ffromani
Copy link
Contributor Author

/retest-required

Copy link
Contributor

openshift-ci bot commented Jul 22, 2024

@ffromani: all tests passed!

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.

@ffromani ffromani changed the title makefile: ensure bindata NO-JIRA: makefile: ensure bindata Jul 22, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 22, 2024
@openshift-ci-robot
Copy link
Contributor

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

In response to this:

0_config requires now pkg/manifests, so we need
to make sure bindata is generated

extracted from #1019 because it helps other PRs too: #1019 (comment) (xref: #1089)

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.

@ffromani
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

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

In response to this:

/jira refresh

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 18febd2 into openshift:master Jul 22, 2024
16 checks passed
@ffromani ffromani deleted the e2e-tests-bindata branch July 22, 2024 10:04
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-node-tuning-operator
This PR has been included in build cluster-node-tuning-operator-container-v4.17.0-202407221413.p0.g18febd2.assembly.stream.el9.
All builds following this will include this PR.

zeeke added a commit to zeeke/cnf-features-deploy that referenced this pull request Aug 19, 2024
Since [1], cluster-node-tuning operator needs a compile
step to run functional tests.
Though a general refactor in how we run submodules functional
tests would be required at this point, this commit fix the problem in
the short term by invoking `make vet` right after the checkout.

[1] openshift/cluster-node-tuning-operator#1116

Signed-off-by: Andrea Panattoni <[email protected]>
zeeke added a commit to zeeke/cnf-features-deploy that referenced this pull request Aug 19, 2024
Since [1], cluster-node-tuning operator needs a compile
step to run functional tests.
Though a general refactor in how we run submodules functional
tests would be required at this point, this commit fix the problem in
the short term by invoking `make vet` right after the checkout.

[1] openshift/cluster-node-tuning-operator#1116

Signed-off-by: Andrea Panattoni <[email protected]>
natifridman pushed a commit to natifridman/cnf-features-deploy that referenced this pull request Sep 29, 2024
Since [1], cluster-node-tuning operator needs a compile
step to run functional tests.
Though a general refactor in how we run submodules functional
tests would be required at this point, this commit fix the problem in
the short term by invoking `make vet` right after the checkout.

[1] openshift/cluster-node-tuning-operator#1116

Signed-off-by: Andrea Panattoni <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants