ctr plugin ls: plugin status should be skip, not error#5200
ctr plugin ls: plugin status should be skip, not error#5200crosbymichael merged 1 commit intocontainerd:masterfrom
Conversation
|
Hi @pacoxu. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
Build succeeded.
|
cfc678c to
8d3b432
Compare
|
Build succeeded.
|
8d3b432 to
cc2652d
Compare
|
Build succeeded.
|
cc2652d to
621577b
Compare
|
Build succeeded.
|
Signed-off-by: pacoxu <[email protected]>
621577b to
a76cefd
Compare
|
Build succeeded.
|
|
/retest |
|
@pacoxu: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
CI / Windows Integration (pull_request) failed for the above error message. It seems to be a timeout? |
|
@samuelkarp |
Skip error can be identified as
skip/kind bug