-
Notifications
You must be signed in to change notification settings - Fork 43
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
Kexec/Kdump Tests #237
Kexec/Kdump Tests #237
Conversation
…estflinger or somewhere else
@spmcmillan Just making sure I understand before looking at the code - are these the first tests that need to be run remotely over |
Yes, these are probably the only tests that will need to be run remotely as they require the system to reboot or crash whenever they are invoked. I'm not sure the ideal place to put these. They won't be picked up by the pytests so they are already isolated and won't be included with the checkbox tests either. They are very special case and I can see them running on testflinger on the agent. I thought this was an ok to put them because they have the ".sh" extension. But, if you have other ideas please suggest them! |
Ah ok - I was thinking they would but I guess with the .sh extension tox/pytest will not pick them up. 👍 |
…ine when the system went down instead of a timeout
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! I like the changes.
https://warthogs.atlassian.net/browse/PEK-852
Adding kexec/kdump tests for the host. This requires the host to be rebooted effectively multiple times. So, this was written as a shell script that can be used, eventually, in testflinger, or in a runner.