-
Notifications
You must be signed in to change notification settings - Fork 608
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
Debug Windows CI failure with containerd 1.5.8 #534
Debug Windows CI failure with containerd 1.5.8 #534
Conversation
3ee31d7
to
60a65cf
Compare
is there a way to retrigger a single test? I think the changes here will work based on #533 (comment) |
Signed-off-by: Akihiro Suda <[email protected]>
60a65cf
to
72f12dd
Compare
A reviewer/committer can retrigger a single Cirrus test (and the entire GHA tests). Would you be interested in being a reviewer (and eventually a comitter) of nerdctl ? |
As expected the exec's are working when used directly. It seems the test framework might be holding onto a file reference somewhere: CI run with exec directly works:
|
Not sure I've done enough yet 😊 and I may only be helpful from Windows side given my current knowledge but would be interested. |
- nerdctl exec nerdctl-test-exec echo hello3 | ||
- nerdctl rm -f nerdctl-test-exec | ||
|
||
- nerdctl run -d --name nerdctl-test-exec gcr.io/k8s-staging-e2e-test-images/busybox:1.29-2 sh -euxc "sleep 1h" |
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.
- nerdctl run -d --name nerdctl-test-exec gcr.io/k8s-staging-e2e-test-images/busybox:1.29-2 sh -euxc "sleep 1h" | |
- nerdctl run -d --name nerdctl-test-exec gcr.io/k8s-staging-e2e-test-images/busybox:1.29-2 sh -eux "sleep 1h" |
still working on why but this should let it pass
Thanks, opened #562 to add you as a Reviewer |
Debug #533 (comment)