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
[node-e2e] add test cases for serialize and parallel image pulling #121604
base: master
Are you sure you want to change the base?
Conversation
724eb51
to
390ac56
Compare
/remove-area dependency |
390ac56
to
d1507d8
Compare
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial Add an logic to check if the pull happened together. If not, skip it. |
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial |
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial |
- wait for pod pulled: running/failed(no restart)
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial |
/hold Image pulling sometimes is so quick and it used only ~100ms. Changing to use a large image may help. |
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial Both passed. |
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial |
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial Last two runs of both are passed. It would be more stable to use a larger image instead. |
flake for unrelated test: /test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial Recent 6+ run are not flake. @ruiwen-zhao @SergeyKanzhelev would you take a look again? |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pacoxu, ruiwen-zhao 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 |
/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial |
after using a big image, the time wait time should be larger. /test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial |
@pacoxu: The following tests 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. |
The changed Image is so big and the test timeout after 10 minutes. I need to find another image for the test 😓. |
So the flake before was that the image was too fast to download? Since the test is mostly timestamps comparison, why was it flaking? Was the download spees faster than a second? If this is the case, the next step may be to install the ImageService proxy that will introduce the delay. It is not such a bad idea long term as it will allow to test other failure modes and edge cases in future. But it will require maintaining this proxy. @ruiwen-zhao @pacoxu wdyt? |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:
xref kubernetes/enhancements#3673
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: