Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handle CTRL-C Signal in Run command #17

Open
damianoneill opened this issue Aug 1, 2018 · 1 comment
Open

Handle CTRL-C Signal in Run command #17

damianoneill opened this issue Aug 1, 2018 · 1 comment

Comments

@damianoneill
Copy link
Owner

At the moment if there are blocking netconf requests (for e.g. the agent on the device is dead), the tool can wait a long time to complete, so most people CTRL-C. It would be useful at this point to generate a results which contained a partial testsuite. This will be useful if the suite failed part way through as you could identify where / when the issue started.
@damianoneill damianoneill changed the title Handle CTR-C Signal in Run command Handle CTRL-C Signal in Run command Aug 1, 2018
@damianoneill
Copy link
Owner Author

https://gobyexample.com/signals

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@damianoneill