-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
bump QEMU version to v2.9.1 #50597
bump QEMU version to v2.9.1 #50597
Conversation
Hi @dixudx. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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/test-infra repository. I understand the commands that are listed here. |
@@ -14,7 +14,7 @@ | |||
|
|||
REGISTRY ?= gcr.io/kubernetes-e2e-test-images | |||
GOARM=7 | |||
QEMUVERSION=v2.7.0 | |||
QEMUVERSION=v2.9.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really sure whether we need to push all the relevant images under test/images
with this new qemu binary. @luxas WDYT?
arm=gcr.io/google-containers/debian-base-arm:0.1 | ||
arm64=gcr.io/google-containers/debian-base-arm64:0.1 | ||
ppc64le=gcr.io/google-containers/debian-base-ppc64le:0.1 | ||
amd64=gcr.io/google-containers/debian-base-amd64:0.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may need to bump the version for resource-consumer image in test/images/resource-consumer/VERSION
build/root/WORKSPACE
Outdated
@@ -54,6 +54,7 @@ http_file( | |||
url = "https://storage.googleapis.com/kubernetes-release/network-plugins/cni-amd64-0799f5732f2a11b329d9e3d51b9c8f2e3759f2ff.tar.gz", | |||
) | |||
|
|||
// TODO(dixudx): update the sha and tag (to v8) when the image get pushed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should use #
for comments? Or spawn an issue for tracking
bedffcc
to
e64ff22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dixudx for your PR!
I don't think we need to bump the versions.
- It shouldn't affect the result (this is only syscall emulation)
- There is no direct benefit we get from using a newer QEMU that would need an image bump. This setting will just be picked up the next time the image is built/pushed.
The rationale for upgrading is to hopefully get more stable and reliable builds, have better emulation support for s390x and pick up performance improvements tha have been made in recent versions.
/ok-to-test |
/retest |
1 similar comment
/retest |
57cca0f
to
f0de8f3
Compare
f0de8f3
to
e4c6337
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ping @ixdy; think we need to bump versions for this?
build/common.sh
Outdated
@@ -85,6 +85,7 @@ readonly KUBE_CONTAINER_RSYNC_PORT=8730 | |||
# | |||
# $1 - server architecture | |||
kube::build::get_docker_wrapped_binaries() { | |||
## TODO(dixudx): update the tag to v8 when the image get pushed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still valid; do we need to do this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the base image of debian-iptables
, we'd better bump a new version.
QEMU is really only used when building the images, right? in that case, no, I don't think bumping the tags is needed. |
Yes, we are just using it during building. @ixdy Actually since the |
e4c6337
to
22bdaec
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dixudx, luxas Assign the PR to them by writing Associated issue: 38067 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 |
/retest |
1 similar comment
/retest |
@ixdy Please approve this. Thanks! |
/retest |
ping @ixdy Need your approval. PTAL. Thanks! |
/test all |
/retest |
Automatic merge from submit-queue |
@dixudx: The following test failed, say
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. |
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #xref #38067
Special notes for your reviewer:
/assign @luxas
Release note: