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

Set empty TARGETVARIANT and BUILDVARIANT #301

Merged
merged 1 commit into from
Feb 20, 2025

Conversation

Honny1
Copy link
Contributor

@Honny1 Honny1 commented Feb 19, 2025

This PR sets empty values as the default value for the TARGETVARIANT and BUILDVARIANT buildin arguments since Docker does not insert these values for ARM64.

Related PR:

@openshift-ci openshift-ci bot requested review from mrunalp and nalind February 19, 2025 10:55
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 19, 2025
Copy link
Contributor

openshift-ci bot commented Feb 19, 2025

Hi @Honny1. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@Honny1 Honny1 force-pushed the fix-variants-arm64 branch from 6ef308e to db4750d Compare February 19, 2025 12:55
@nalind
Copy link
Member

nalind commented Feb 19, 2025

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 19, 2025
@nalind
Copy link
Member

nalind commented Feb 19, 2025

I'm seeing errors from unit tests in the main directory when I run them in my arm64-on-amd64 VM with these changes. Are you getting passing results when running go test ./... at the top level?

@Honny1
Copy link
Contributor Author

Honny1 commented Feb 19, 2025

I also failed unit tests. (Including master) I checked the failed tests and they expect that a variant should be set. I think the tests are wrong. WDYT?

@nalind
Copy link
Member

nalind commented Feb 19, 2025

Yes, if they expected behavior which we now consider to be incorrect, they need to be updated to expect what we consider to be correct.

Docker does not set these values for ARM64.

Signed-off-by: Jan Rodák <[email protected]>
@Honny1 Honny1 force-pushed the fix-variants-arm64 branch from db4750d to 6062143 Compare February 20, 2025 09:58
Copy link
Contributor

openshift-ci bot commented Feb 20, 2025

@Honny1: 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.

@Honny1
Copy link
Contributor Author

Honny1 commented Feb 20, 2025

I adjusted the tests to expect the correct values.

@nalind
Copy link
Member

nalind commented Feb 20, 2025

/lgtm
Thanks!

@nalind
Copy link
Member

nalind commented Feb 20, 2025

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2025
Copy link
Contributor

openshift-ci bot commented Feb 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Honny1, nalind

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 20, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 7ebfb09 into openshift:master Feb 20, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants