Fixes to run node e2e tests#4627
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
|
@dmcgowan: No jobs can be run with
DetailsIn response to this:
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. |
|
/test pull-containerd-build |
|
/test pull-containerd-node-e2e |
|
Build succeeded.
|
|
/test pull-containerd-node-e2e |
5f08d18 to
25d641d
Compare
|
/test pull-containerd-node-e2e |
|
Build succeeded.
|
25d641d to
83f4774
Compare
|
/test pull-containerd-node-e2e |
|
Build succeeded.
|
83f4774 to
29c55ac
Compare
|
/test pull-containerd-node-e2e |
|
Build succeeded.
|
29c55ac to
283a717
Compare
|
/test pull-containerd-node-e2e |
|
Build succeeded.
|
Signed-off-by: Derek McGowan <[email protected]>
283a717 to
04a3f7c
Compare
|
/test pull-containerd-node-e2e |
|
Build succeeded.
|
|
@dmcgowan: 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. DetailsInstructions 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. |
|
Possible fix here kubernetes/kubernetes#95613 see kubernetes/kubernetes#95321 |
|
we can merge this fix now imo.. the failures are not due to this PR or the merging of CRI into containerd. |
|
/test |
|
@mikebrow: The
DetailsIn response to this:
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. |
|
/test pull-containerd-build |
|
LGTM |
Running through tests first