-
Notifications
You must be signed in to change notification settings - Fork 74
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
Fix Method of judging command execution failure #52
Conversation
should judge restore and run command execution failure depend both on error and status Monitor.Wait() return Signed-off-by: Ace-Tang <aceapril@126.com>
Codecov Report
@@ Coverage Diff @@
## master #52 +/- ##
=========================================
- Coverage 6.18% 6.12% -0.06%
=========================================
Files 7 7
Lines 631 637 +6
=========================================
Hits 39 39
- Misses 585 591 +6
Partials 7 7
Continue to review full report at Codecov.
|
@crosbymichael , would you help to check this |
LGTM |
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.
/LGTM
- github.com/containerd/go-runc containerd/go-runc@7d11b49...9007c24 - containerd/go-runc#52 Fix Method of judging command execution failure - fixes "init.pid: no such file or directory: unknown" errors Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
- github.com/containerd/go-runc containerd/go-runc@7d11b49...e029b79 - containerd/go-runc#52 Fix Method of judging command execution failure - fixes "init.pid: no such file or directory: unknown" errors - containerd/go-runc#54 avoid setting NOTIFY_SOCKET from calling process Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Derek McGowan <derek@mcgstyle.net>
- github.com/containerd/go-runc containerd/go-runc@7d11b49...e029b79 - containerd/go-runc#52 Fix Method of judging command execution failure - fixes "init.pid: no such file or directory: unknown" errors - containerd/go-runc#54 avoid setting NOTIFY_SOCKET from calling process Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Derek McGowan <derek@mcgstyle.net> Upstream-commit: 1617be92d301de1386adabad5f241d3653b6c8ff Component: engine
- github.com/containerd/go-runc containerd/go-runc@7d11b49...e029b79 - containerd/go-runc#52 Fix Method of judging command execution failure - fixes "init.pid: no such file or directory: unknown" errors - containerd/go-runc#54 avoid setting NOTIFY_SOCKET from calling process Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Signed-off-by: Derek McGowan <derek@mcgstyle.net> Signed-off-by: zach <Zachary.Joyner@linux.com>
should judge restore and run command execution failure depend both on error and
status Monitor.Wait() return.
Since Monitor.Wait() always return nil as long as command execute.
Signed-off-by: Ace-Tang aceapril@126.com
I only test it with pouch, before the patch
and with this patch in containerd, it can get correct error log