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

Build test targets for all server platforms #51873

Merged
merged 2 commits into from
Sep 6, 2017

Conversation

luxas
Copy link
Member

@luxas luxas commented Sep 3, 2017

What this PR does / why we need it:

🤦

I really should have checked this before code freeze, but tbh forgot it in the rush. Also I thought this was the case already...
As part of kubernetes/enhancements#288; these binaries should be built for all server platforms indeed.

This is just a straightforward add to that list.
Can we please get this into v1.8?
There is virtually no risk involved here really...

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Release note:

Build test targets for all server platforms

@ixdy @jdumars @mkumatag

@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Sep 3, 2017
@luxas luxas assigned jdumars and ixdy Sep 3, 2017
@k8s-github-robot k8s-github-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Sep 3, 2017
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 3, 2017
Copy link
Member

@mkumatag mkumatag left a comment

Choose a reason for hiding this comment

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

Have a minor comment otherwise lgtm.

@@ -33,6 +33,10 @@ import (
"k8s.io/client-go/dynamic"
)

const (
Copy link
Member

Choose a reason for hiding this comment

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

why this change part of this PR?

Copy link
Member Author

Choose a reason for hiding this comment

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

otherwise arm 32 bit fails due to that the constant is larger than int32 (default on arm) can handle

Copy link
Member

Choose a reason for hiding this comment

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

okay

@calebamiles
Copy link
Contributor

/retest

@ixdy
Copy link
Member

ixdy commented Sep 3, 2017

/lgtm

though we should probably start breaking up kubernetes-test.tar.gz into arch-specific tarballs, since it is getting rather large.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 3, 2017
@k8s-github-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ixdy, luxas
We suggest the following additional approver: sttts

Assign the PR to them by writing /assign @sttts in a comment when ready.

Associated issue: 288

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

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@ixdy
Copy link
Member

ixdy commented Sep 3, 2017

(also note you only need to build the test binaries for architectures you're launching tests from - e.g. if I have a cluster running on arm, but my workstation is amd64, I don't need to build the test binaries for arm.)

@cblecker
Copy link
Member

cblecker commented Sep 4, 2017

/test pull-kubernetes-cross

@luxas
Copy link
Member Author

luxas commented Sep 4, 2017

(also note you only need to build the test binaries for architectures you're launching tests from - e.g. if I have a cluster running on arm, but my workstation is amd64, I don't need to build the test binaries for arm.)

@ixdy Yeah, I know, but this is required as we're starting to run e2es on Packet ARM servers; where the e2e binaries are running in-cluster => cross-built e2e binaries are needed.

though we should probably start breaking up kubernetes-test.tar.gz into arch-specific tarballs, since it is getting rather large.

Can you please open an issue with more info about that so we can target it for v1.9?

@calebamiles calebamiles added this to the v1.8 milestone Sep 5, 2017
@calebamiles
Copy link
Contributor

/test pull-kubernetes-e2e-kops-aws

linux/arm
linux/arm64
linux/s390x
linux/ppc64le
Copy link
Contributor

Choose a reason for hiding this comment

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

will this cause any build performance regressions?

Copy link
Member Author

Choose a reason for hiding this comment

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

no, this is for release (and the post-ci, independently running kube-cross job) code only. All other jobs etc perform the "fast path" and only build for amd64

@luxas
Copy link
Member Author

luxas commented Sep 5, 2017

Adding the approved label as the release team and @ixdy were happy with the changes here, and we want to get this in for tomorrow's beta.1

@luxas luxas added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 5, 2017
@luxas
Copy link
Member Author

luxas commented Sep 5, 2017

/retest

@fejta-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to @fejta).

Review the full test history for this PR.

@k8s-ci-robot
Copy link
Contributor

@luxas: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
pull-kubernetes-e2e-kops-aws 64be85e link /test pull-kubernetes-e2e-kops-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

@k8s-github-robot
Copy link

Automatic merge from submit-queue (batch tested with PRs 51984, 51351, 51873, 51795, 51634)

@k8s-github-robot k8s-github-robot merged commit b6a0bb1 into kubernetes:master Sep 6, 2017
@jdumars
Copy link
Member

jdumars commented Sep 6, 2017

@luxas could you please assign a SIG label to this? Thanks!

@luxas luxas added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Sep 6, 2017
@luxas
Copy link
Member Author

luxas commented Sep 6, 2017

@jdumars added

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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/release Categorizes an issue or PR as relevant to SIG Release. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants