You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.
It's possible and sometimes expected for a system to panic while running ztest or the zfstest suite. When this occurs, we should automatically process any core dumps when gathering the test results, after the test has finished. This would save us the trouble of having to perform this analysis manually, and also potentially losing this state if the VM containing the core dump is destroyed prior to being inspected.
The text was updated successfully, but these errors were encountered:
prakashsurya
changed the title
utomatically process core dumps when they exist, after test runs
process core dumps when they exist, after test runs
Nov 7, 2016
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It's possible and sometimes expected for a system to panic while running
ztest
or thezfstest
suite. When this occurs, we should automatically process any core dumps when gathering the test results, after the test has finished. This would save us the trouble of having to perform this analysis manually, and also potentially losing this state if the VM containing the core dump is destroyed prior to being inspected.As an example, see this comment: openzfs/openzfs#219 (comment)
The text was updated successfully, but these errors were encountered: